The Power Actions wizard is implemented as a list of steps that start from the main button. You can configure each of them directly from on the custom field configuration page.
The configuration page displays a list of buttons with all their steps. A button is actually the first screen of the wizard.
...
- edit the scripts – condition, screen, and action
- change the description
- rename it
- add or remove a step
- reorder the steps to suit your needs.
When you add a step to a given button, a new line will be added in the configuration table showing this step. For this new step you can also configure the scripts, change the description or rename it.
The steps of a button can be reordered inside the button.
...
Adding new steps
In order to add a new step all you need to do is press , click the Add Next Step button (the "+" icon) for the desired needed button. A new line containing the new step will be added into the with a step is added to the configuration table.
The name of the step will start starts with the word "Step" and its position in the list. This is an non-editable data .You but for your convenience, you can change the description of the step by clicking on the clicking Change Description button.
For each step you can also configure the scripts.
| Note |
|---|
| You can reorder the added steps within the a button, but the step names will always retain the current position of the step. |
...
The condition script for a step is similar to the one for a button. This means that it still allows you to , you can decide whether an action will should be available for the user or not. By default, when you add a new action, it will have the following default condition script.
...
The script should return one of the predefined variables: ENABLED, DISABLED, or HIDDEN. The main difference between the condition script for a button and the condition script for a step is how we interpret the DISABLED / HIDDEN values.
- Enabled actions are visible and available for the user to execute
- Disabled actions mean that the screen for the action will not be visible and thus unavailable for the user to execute
- Hidden actions mean that the screen for the action will not be visible but the action script will still be executed
Of course, since we are using SILwith the help of Simple Issue Language (SIL), the return value of the script can be conditional.
...
Sharing values between wizard screens
Certain You can configure a wizard so that certain values on the wizard screen might depend on other values from another screens, therefore . For this we implemented additional routines that help with the sharing mechanism.