Button Layout Element¶
New in Atfinity 17.
Definition¶
A Button Layout Element runs rule actions when a user clicks it in a case. A rule decides for itself when to act, a button waits for a person to decide, so reach for one where the action needs human judgement: starting a background check on request, or recording a decision on a single record.
Place a button in the layout of a process tab, where it belongs to the instance it sits on, or in the layout of a structure information, where it belongs to one occurrence and so appears on every occurrence. Buttons are not available in end user wizards or in the layout of an instance page.
A button offers the same actions a rule does, including integrations and custom API requests. They run once per click, and what they change stays in the case: a button has no condition that can turn false later and take its own work back. On a completed case the button is still shown, but only its Send Email actions and its custom API requests run.
The condition of a button decides whether it is shown. Leave it empty to always show the button. It cannot contain a declaration, and uses self for the instance the button is placed on, plus this_structure for the occurrence when the button sits in a structure layout. The actions have the same two references available.
The label of a button is not translated, so every language shows the same text. When a structure is displayed as a table, all buttons of a row share a single column at the end of that row.
Example¶
A World-Check search returns its matches as occurrences of a structure, and someone has to say which of them is really the client. A button placed in the structure layout appears on every match, and its condition hides it again once that match has been assessed:
Its action writes the decision to that one occurrence:
A second button next to it records the opposite decision, and both disappear from the row as soon as one of them is used.