multi-client_features
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
multi-client_features [2015/12/12 13:36] geelling |
multi-client_features [2017/02/20 16:50] (current) |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| Client users are set up in User Management. Where multi-client features have been enabled, a client setting is required. This can be set to "All" for credit union users who should have access to forms relating to all applicants, or to the relevant partner for users who should have access only to forms relating to their own customers. | Client users are set up in User Management. Where multi-client features have been enabled, a client setting is required. This can be set to "All" for credit union users who should have access to forms relating to all applicants, or to the relevant partner for users who should have access only to forms relating to their own customers. | ||
| - | Users restricted to a single client will have access only to forms containing a client field, denoted by the special treatment value ADDRESS_LOOKUP_CLIENT. The value of this field will determine which forms a user can access in the Workflow Manager. | + | Users restricted to a single client will have access only to forms containing a client field, denoted by the special treatment value "LIB=address_client". The value of this field will determine which forms a user can access in the Workflow Manager. |
| + | |||
| + | **Setting a client admin email address for workflow notifications** | ||
| + | |||
| + | When using multi-client features, you may send automated notification emails to a client-specific admin email address from workflows by selecting "Client" from the TO or CC dropdowns. | ||
| + | |||
| + | Where set, this will use the CLIENTVALUE:admin_email lookup - otherwise the standard admin email address will be used. | ||
| **Substituting client information in form text** | **Substituting client information in form text** | ||
| Line 13: | Line 19: | ||
| Where forms are not linked to a source form, the client can be set in the form URL, using the value pair clientcode=999 - eg [[https://cuforms.org.uk/runform.php?article_id=518&htmltype=html5&clientcode=001]] | Where forms are not linked to a source form, the client can be set in the form URL, using the value pair clientcode=999 - eg [[https://cuforms.org.uk/runform.php?article_id=518&htmltype=html5&clientcode=001]] | ||
| + | |||
| + | In both cases, if the value of any field in the new form with the special treatment value "LIB=address_client" will be set to the appropriate client. | ||
| Client-specific substitutions can also be made using [[dynamic_links|dynamic links]] in workflow emails. | Client-specific substitutions can also be made using [[dynamic_links|dynamic links]] in workflow emails. | ||
| + | |||
| + | nb - the special treatment value "ADDRESS_LOOKUP_CLIENT" will also be recognised for backward compatibility with older workflows. | ||
multi-client_features.1449923796.txt.gz · Last modified: 2017/02/20 16:49 (external edit)
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
