Central and ActiveVOS Screenflow

9.2.5
- 9.2.6
- 9.2.4.6

Back Next

Tabs

May step types include three basic tabs, Information, Input, and Input Screen. The following image shows the tabs in a Service Call step:

Information Tab

The Information
tab has a description of the Service Call step and a description of the input and output fields for the step. The descriptions in this tab can help you when you are using the object's input or output fields. Because this information is automatically generated, only input and output field names and types appear in this tab. There are no descriptions for them.

The information tab, depending upon the object the step is operating upon, lets you choose to Run on a single object or Run on each object in list until either the list ends or until an outcome occurs.

Selecting "Run on a single object" tells Process designer that it will only be applying a service call or a subprocess on one object. It the other option is selected, the step operates on each object in an object list. If this option is selected, it is indicated in the canvas with a looping arrow button. Clicking on this buttons opens the invoked step.

Input Tab

The Input
tab shows the names of input fields that are most often used when using this kind of step. For Service Call steps that create objects, the input fields shown are the fields that are most frequently needed when the object is created. (If you do not need a field and it is optional, you can delete it.) You can choose additional (optional) input fields from the list. For example:

Use the

delete icon to remove a field. This removes input fields that you do not want to pass to the Service Call step. The names of required fields are displayed with an asterisk. These fields cannot be deleted.

Use the Add Input
list to add additional input fields (or re-add input fields that were accidentally deleted). The source for the field's data is obtained by selecting Constant
, Field
, Screen
, Query
, or Formula
in the list following the field's name. (Not all of these always appear.)

The fields shown in the Add Input list are more than just those than are shown in the Information tab as it contains all fields within the currently selected object and includes the fields that were declared within the properties.

After a step executes, all steps that follow can access output fields created in the step upstream. This enables you to use the screen editor to insert them into the step's canvas.

Input Screen Tab

The Input Screen tab is only available for guides.

If you select Screen
as the source of the input field source, you must place that field on a screen using the Input Screen
tab. For example:

Service Call step showing Input Screen tab

When users see this step, they will see three places in which they can enter information.

To add an input field to the screen editor, click on it. The editor adds input field names as a label followed by an input area for the type of data being requested; for example, a text entry field or a picklist.

Hint: You can make what you enter more readable if you align text and fields.

Here are a few things you should know:

Because the input fields are being added to the editing screen, you can add instructions and comments and rearrange the way the screen appears.

Notice the Insert Read-Only Field
picklist. Use a read-only field to display information that will help the user or present object information. For example, you can display the name of the user who is running the guide (using the "Current User" field) at the top of a screen that is asking for the information needed for creating a new Event.

You can double click within any input field placed on the screen to display the Field Properties
dialog.

Use the "Don't allow skip/Allow Skip Button" picklist to define whether the guide's user can go to the next step without performing any of the step's activities. The following figure illustrates each of these behaviors.

If you select "Don't allow skip", the user must perform the actions indicated within the step. Because this action is required, only one possible action can follow, which is that Guide Designer executes the next step. In contrast, if you select "Allow Skip Button", there are two possible answers: one if the user performs the action and the other when no actions are performed. Because the action is optional, Guide Designer displays a button that the user can press to skip the step. While the default text for the button is "Skip", you can change it by entering text within the data entry area displays that displays after you select "Allow Skip Button."

Events Tab

On the Events tab, you can set timers that determine when the action occurs, and also specify Messages for use with message providers and correlation.

In the previous image, two timers were added. The top shows "After". Here you are specifying a duration; that is, the timer event occurs after the amount of time selected expires. In contrast, the bottom timer event occurs at the time you specify and you can also specify the number of days. Both of these timers are non-interrupting, which means each branch executes separately from other branches. This mode of executing is similar to a Parallel paths step that does not converge to a common step after the branch ends its execution. The difference is that if the timer branch branches do not execute if the non-timer step concludes.

Stated in another way, the timer interrupts the step upon which the timer is set and the timer's path executes.

If you had created interrupting timers, the branches merge back together. Here's an example:

A step can have both interrupting and non-interrupting timers, as the following shows:

Here are some usage notes:

To add a timer, press the Add Timer
button.

To delete a timer, press the "x
" button.

To reorder the branches, press the Reorder button. This displays a dialog box that lets you change the way branches display in the canvas. The order in which the branches display has no effect on the order in which branches execute.

Process Designer cannot interrupt a subprocess invoked in the agent from a process executing in Informatica Cloud. An interruption only occurs if all processes are executing in the agent or in the cloud.

Rename Saved Search

Table of Contents

Central and ActiveVOS Screenflow

Central and ActiveVOS Screenflow

Tabs

Tabs

Information Tab

Input Tab

Input Screen Tab

Events Tab