Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
JonH67 Absent Member.
Absent Member.

Single flow provision members PRD

Carrying on with the requirement to create temp users for internet
access, I'm using an auto started workflow, once users have been added
via the delimited text driver. I've created a single flow provision
member PRD. Is there any way of populating the multiple recipients
automatically? I've also noticed that even though the PRD says it can
provision multi user objects, the recipient entry in the form is set to
non-multivalued and can't be changed.
The issue is the approver only wants to see one email, around 50 temp
users could be created at once. I've explained that every event has to
come thorugh the channel and be processed on a singular basis. I'm
starting the workflow from within the userapp driver. I can't use the
group as the only group that exists is the one the users are provisioned
into for sync to the access tree.
Has anyone done this before? I'm thinking that I could do a search on
all newly created users and turn them into some sort of blob which is
then picked up by the autostart workflow. I just can't think of what
blob and whether or not an auto started workflow is seen as a multi
member PRD. Is the provision members function something the portal
interprets and when seen in a policy it only passes single events to
completion as IDM is meant to?

JonH67's Profile: http://forums.novell.com/member.php?userid=105091
View this thread: http://forums.novell.com/showthread.php?t=452690

Labels (1)
2 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Single flow provision members PRD


It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your problem been resolved? If not, you might try one of the following options:

- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)

Be sure to read the forum FAQ about what to expect in the way of responses:

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your Novell Product Support Forums Team

JonH67 Absent Member.
Absent Member.

Re: Single flow provision members PRD

I've gone back to reading the documentation, especially the design
guide, version 4.0.1 Apr 11. It's a little conflicting as in section
4.2.2 about single flow provision members flow strategy, it states that
this can be a group dn, but in section 6.9 in states that the workflow
can provision individual users of the default user container, all
members of a group or all members of a vault container. The information
to create the single flow provision member, says to create the prd as
normal and change the flow strategy, that's it! I've changed the start
pre activity and removed recipient, this allows multi user objects to be
selected, but they generate singular approver requests. If I use a
group, it errors out about not being able to check object cn=xxx. What
else needs to be changed to support this, I hoped that the entities and
relationships that already exist would support this.

JonH67's Profile: http://forums.novell.com/member.php?userid=105091
View this thread: http://forums.novell.com/showthread.php?t=452690

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.