Changes

Using the Assigned To field

944 bytes added, 18:53, 8 September 2014

no edit summary

At the bottom of a form, there is the ability on an Outcome by Outcome basis to sue the Assigned To field.== Overview ==

At the bottom of a form, there is the ability on an outcome by outcome basis to use the "Assigned To" field.  This field is used in conjunction with callbacks to create a Reminder for a record but have it allocated to someone elseto do.

So to set up the Assign To option correctly, a member can only assign to another if they are person for people in a the same Security Group as themselves.   == Enabling Assigned To ==  The first step is to create the security groups. This is discussed in [[Organogram_with_Group_Profiling]]  With the Groups properly created we then want to assign them to the form. For the grouped reporting, it is possible to use the parent of the security tree and the system will perform the lookup to find out which branch the user is in. To ensure separate explicit group listing is possible without going back to Everyone listing, you must explicitly add each security groupto the form. The This gives you the control to allow only certain groups to allow "Assigned To" callbacks.  ''Main Menu > System Access Management > Security - Content Access > Form - Add Security Groups to Form > Add each Assign To will only be group separately.''  Next you need to other members in that groupturn the Assign To on for your chosen outcome.

The engine does not traverse the security tree to allow ''Main Menu > Form Management > Form - Outcome Manager > Outcome - Edit > Choose your form > Choose your outcome > Callback - Reminder / Appointment > Has "Assigned To" = True and Has "Date/Time" for explicit groups to be listed and manage sensiblyCallbacks = True.''

• ← Older edit
• Newer edit →

Philip Lacey

Anonymous, bureaucrat, administrator

7,528

edits