User Based Decisions
Table of contents
No headersThis page shows how to use user based decisions in the process designer.
In the image shown we are already inside the Process Designer and have added two Business Objects to the stage.(For more information on these look up Business Objects)

1.To begin we acces the toolbox to bring up the Process flow menu. Now we drag a decision object onto the stage.

2.This will open the pictured Define Decision form.

3.As we wish to make a User Based Decison we tick the box under the description bar.
A User based Decision is uesd within iceberg to prompt a user or a number of users within a role to take action by a set date. In this example we are dealing with our "Red Tag" process and we wish a user to approve it as soon as it has been created.
4.Set the Description.
The Description only relates to the process designer's UI and will show up on the visual representation of the process flow. It will in no way effect the user using the system.
5. Now we use the Define Decision form to select a Business object to display this decision.
6. Set the Date that the decision needs to be made by. From the dropdown menu we can select any date within the process or process flow. For now we've picked "last modified"
(For further information on overdue items see Dates, associated with date expressions)
7. In the Assign To Field use the dropdown menu to and open the option list. You will notice that roles have an * beside them while users do not. By selecting red tag* from the list all users with the red tag role will be able to access and make this decision.
8. Do you wish to create a task for this decision? allows you set this decision as a task for your users. You can also send the user(s) a message to explain the decision.The task will show up as
on the users homepage.
9. Now we can set the posible outcomes for our decision. In this case our Positive outcome is approve and the Negative outcome is reject. A useful asthetic funtion here is that putting a > beside the Positive outcome gives it a nice looking check mark graphic while adding< beside the Negative outcome gives it a less appealing X graphic. Now click Apply to create the new decision and return to the stage.
![]()
10.To enable the Decision draw a line from the last step down to the Decision. By simply drawing lines from the decision outcomes to another Object or Process we can easily set what each response does. For example if we want the Process to inform a user that the Decision is overdue we add a Direct User Object, type a biref overdue message in the Direct User Object and click Apply.
Now we simply draw a line out from one of the Overdue points to the Direct User Object and click Save.
Our User Based Decision is now functioning. In this example of it working we Create a new Red Tag.

And are then told that the Red Tag is Overdue. This is because the date selected for the red tag has already passed.
![]()
- Tag
-
none
- What links here