Macros

1. Play Macro:

All the macros associated and configured with the ZIEWeb sessions are listed and can be played at the client’s end. The macros are executed in the background, so the intermediate screens do not get displayed.

To play the macros, select a macro from the list or use the Search bar to find the required macros that are categorized into the below 3 groups:

  1. Session Macro: This type of macros are the ones that are saved in the session library while recording. The macro will be present in the session that the macro was recorded in, on the server-side. To play a session macro, click on the macro’s icon.
  2. Server Macro: This type of macros are the ones that are stored in the central repository created by an Admin to access ZIEWeb sessions. The Server macro can be played from any type of client or session, but currently, only URL-based Server macro library is supported in ZIEWeb-Client. To play a server macro, click on the macro’s icon from the central repository.
  3. Local Macro: This type of macros are the ones that are present in the client machine. To play a local macro, click “choose file” to browse and import the macro from the client machine and then click on the macro’s icon.

2. Record Macro:

User will be able to record two kinds of macros.

a) Current Session Macro:

Macro content will be saved in the corresponding ‘cfg’ file at ZIEWeb server location (in case of Config based model).

Macro content will be added to the browser cache (in case of HTML & Combined based model).

b) Local Macro:

Macro file i.e. ‘mac’ file will be generated at the browser download location.

After clicking the RECORD button, the RECORD button will be disabled, and the STOP button will be enabled.

3. Pause Macro:

Users can click on PAUSE button to pause the recording of the macro.

No events will be recorded unless and until the user again clicks PAUSE button to resume the recording.

4. Stop Macro:

User can click on STOP button to stop the recording of the macro.

The STOP button will be disabled, and the RECORD button will be again enabled to record a new macro.

5. Prompt Macro:

Users can click the PROMPT button to record a prompt.

Row and Column will be auto-populated from the host screen. User can still modify the values.

Prompt Name: It is a mandatory field for the user to enter.

Default Value:

In the Default Response field, which is optional, user can type the text of a default response that the user wants to appear in the input field of the prompt window when the prompt window is displayed. If the user does not type any keyboard input into the input field of the prompt window, but rather just clicks OK to indicate that the input is complete, then the macro runtime processes the default response that is contained in the input field.

Prompt Title: It is optional for the user to enter.

Value required:

If user selects true in the Value Required checkbox (the default

is false) then:

The macro runtime displays the text string (required), to indicate to the end user that, input is required for this input field.

Clear Host Field: You can have the macro runtime clear the contents of the input field before typing begins, by setting the Clear Host Field checkbox to true.

6. Record an extract:

User can click on EXTRACT button to record an extract.

Name: User needs to provide the name of the extract.

Row and Column will be auto populated from the host screen and can be modified.

In the Row (Bottom Corner) input field, user can enter -1 to signify the last row of the data area on the session window. This feature is helpful if users work with session windows of different heights (such as 25, 43, 50) and want tocapture data down to the last row. Similarly, for the Column (Bottom Corner) input field user can enter -1 to signify the last column of the data on the session window.

Data Plane: Users can select from the Data Plane list.

  • TEXT_PLANE (Default data plane)

  • The text plane contains the text on the screen. When user adds a new extract action, TEXT_PLANE is selected as the default data plane.

  • COLOR_PLANE (This feature will be available in a future release)

  • The colour plane contains colour information for each character of the presentation space.

  • FIELD_PLANE (This feature will be available in a future release)

  • The field plane represents the field positions and their attributes in the presentation space.

  • EXFIELD_PLANE (This feature will be available in a future release)

  • The extended field plane contains extended character attribute data.

  • DBCS_PLANE (This feature will be available in a future release)

  • The DBCS plane contains double-byte character set attribute data for each character and field attribute in the presentation space. You can only select DBCS_PLANE when you are running a DBCS session.

  • GRID_PLANE (This feature will be available in a future release)

  • The grid plane contains information for displaying the grid.

7. Edit Macro:

While recording, user might have forgot to add any of the actions or user might feel to remove some of the actions which is not needed. It is tough for user to create again a new macro so we have a feature called macro Editor.

  • For Editing a Macro,

    If user selects macro location as current session,

    1. For html based and combined based model, macro which is present in the browser cache will be listed in the drop down. User can select the macro which needs to be edited.
    2. For config based, macro which is present at the ZIEWeb private directory will get listed.

    After selecting the macro, the selected macro’s corresponding xml file will be opened in the editor.

    After editing a macro, there is a verify button which verifies the xml correctness. If any error is found, then it will throw an error message.

  • For Deleting a Macro,

    Users need to select the macro which needs to be deleted.

    The selected macro will be deleted.

Limitations:

  • ZIEWeb Client support with Tomcat Support with version 9.x.x and below
  • While playing back a macro, the session gets disconnected when continue is pressed in the intermediate screen after we deploy the WAR file in Tomcat Appserver.