Visit Boris website Update customer attribute

Update customer attribute enables attributes to be updated for a customer at a particular point in the form's lifecycle.  For example, the attribute might be used by an office user to indicate to a device user that the customer is 'on stop' so that no orders can be placed for them, or it may be used to trigger an e-mail notification to a particuar customer when the report is a a particular status.

Main

Main screen for this action
*Description

A descriptive text to identify this action

Name of flag

Attribute name as supplied by Boris support.

Value of flag Value to which attribute is to be updated. Report processing variables work here.
Update mode

Update mode determines how Boris will behave when updating the attribute.  The drop-down box contains the following options:

  • Overwrite existing value – takes value entered above and replaces the existing value – useful for recording date of most recent visit
  • Append to existing value – adds new value onto whatever was there before - a full history of visit dates could be held in a string of data
  • Append to existing value with date/time heading – as above, the new value is added to the string of data but with the current date/time
  • Create value only, don't overwrite – will never overwrite/update so it will only be created once as a new value – useful for recording date of first visit

Conditions

This action will only be triggered if the conditions below are met. Leave blank if it is always to be executed.

Condition (1) If you wish to only run an action in a particular situation then you can use these conditions to specify them. The action will only occur if both conditions are satisfied. Typical uses are to only run an action if a particular answer has been given to one of the answers on the template. See Concepts-Conditions
Condition (2) If you wish to only run an action in a particular situation then you can use these conditions to specify them. The action will only occur if both conditions are satisfied. Typical uses are to only run an action if a particular answer has been given to one of the answers on the template. See Concepts-Conditions

Post-action processing (advanced)

After an action has finished running a file can be executed on the server. This could be, for instance, a .exe or a .bat file. Typically this would be used to insert data into another system.

File name to run Enter the full path and filename here.  Ensure that it is correctly spelt and that the file extension (such as .exe or .bat) is also correct.
Command line to run If the file specified above requires additional information on its command line, please enter it here. Contact your Boris expert for further help.
Folder to run from Enter the full path and folder name that the executable programme needs to be launched from.
URL Instead of running an executable file locally, an http request can be sent to the URL specified here. It can contain standard variables.
HTTP verb Choose the http verb to be sent with the request to the URL specified above.  If you do not know what this is, ask your Boris expert.
HTTP request body This will be very different in different circumstances and probably needs to defined at the implementation stage. It can contain standard variables and may contain the data entered on the form.
See Also

Templates

 

 


Parts copyright 2014 Boris Software Ltd. Parts copyright 2014 Firetronic Software Ltd. Parts copyright 1998-2014 Cadence Computing Ltd. All Rights Reserved.

Menus, prompts, fields and options are from a typical installation - some items may not appear as shown. Please contact Boris support for information on additional features.