Standard navigation buttons can be replaced with Macro Buttons on each user form.
Macro Buttons have the advantage of being able to use an image for each of the properties:
Using Macro buttons as Navigation buttons on the user form is known as In Form Navigation.
When the navigation buttons become Macro buttons, Specification Macros will be required to navigate to the relevant forms.
Using the Navigate Forward task we can advance the In Form Navigation.
You will need a Specification Macro to return to the previous form. Repeat the above steps and create a macro using the Navigate Backward task.
Use a name like Previous Form for the macro.
The Specification Macro can now be applied to a Macro button on the user form.
Repeat the above steps for each navigation button required, and on each form you have.
Once In Form Navigation has been tested Standard Navigation can be turned off.
The steps above create basic Navigation button. In reality you will require more buttons that make use of Macros with appropriate tasks applied.
The appearance of a Macro Button can resemble anything you prefer by using the available control properties.
The following discusses how this can be achieved.
The Macro Button has some properties that will make the appearance of your navigation buttons more appealing:
You may require navigation buttons that perform other tasks on the specification. The chart below outlines how to replicate other buttons include in standard navigation.
|Button||Specification Macro Task Required||Notes|
|Cancel||Cancel Specification||Will cancel the current specification and return the user to the Specification Explorer.|
|Save||Use the Invoke Specification Transition task to transition the specification to a paused or automatic State.||Ensure the paused state exists in your Specification Flow and it can be transitioned back to a running state.
The Default Specification Flow contains a Saved state that can be used to construct your own.
|Store||Use the Store Specification task to store the current values entered onto the form.||Unlike the Invoke Specification Transition task this will not exit out of the current specification.|
|Skip||Use the Skip To Form task to skip to a form.||Ensure any critical data on the bypassed forms can still be navigated to.|
|Knowledge Base Article Ref:||KB13120302|