Rich Client Task (Magic xpa 4.x)

You can create a Rich Client task with full transparent runtime functionality by defining a task as a Rich Client task type in the Task property sheet.

Rich Client Subtasks

When creating a subtask for a Rich Client task the new task will be a Rich Client task as well.

Changing the Task Type

Changing the Online/Batch task type to Rich Client

When changing an Online/Batch task type to a Rich Client task:

• The defaults for Rich Client task properties are restored.

• All Online subtasks that appear under the task in the Studio tree are changed to Rich Client tasks.

• All variables with properties broken in the GUI Display style or GUI Display Table style and without any value in the appropriate Rich Client Display styles, will have the GUI styles copied to the Rich Client styles.

• All GUI Display forms will be converted to a Rich Client Display.

• The internal ‘User Action xx’ events (which are not supported in a Rich Client task) will be automatically changed into a user event with the same name. This behavior will happen if such a user event is defined in the Main program.

• Automatic User Action event conversion – If you want a User Action internal event that you defined in an Online task to be automatically converted when you change an Online task to a Rich Client task, then you should define a User event in the Main program and give it the same name as the User Action internal event.
  For example, if you used User Action 5 in an Online task, then before converting it to a Rich Client task, you should define a User event in the Main program and call it User Action 5. When you convert the Online task to a Rich Client task, the reference to the User Action 5 internal event will be automatically converted to the User Action 5 user event.

Changing the Browser task type to Rich Client

When changing a Browser task type to a Rich Client task:

• The defaults for Rich Client task properties are restored.

• An empty Rich Client form will be created as the first form for this task.
  

Changing the task type from Rich Client

When changing the task type from Rich Client to any other task type:

• The defaults for the task properties will change according to the defaults for the new task type.

• The task type of all subtasks will not be changed, since a task type for subtasks is not allowed.

Changing the Form Type from or to Rich Client

• Changing a Browser form to Rich Client will erase all controls, and set all form properties to their default values.

• Changing a Rich Client form to any other type will erase all controls, and set all form properties to their default values.

• Changing a GUI Display form type to Rich Client will convert the form and its controls with the following limitations:

• All of the controls that are not supported in Rich Client tasks will be removed from the form.

• Table Conversion:

• Group and Tab controls that are associated to a table will not be converted.

• List Box controls will be converted to Combo Box controls.

• Radio Button controls will be converted to Combo Box controls. If there are several Radio Button controls with the same data, then the first Radio Button will be converted to a Combo Box. Its range will be a merge of all of the Radio Button (with the same data) ranges. All of the other Radio Buttons with the same data will not be converted.

Related Topics

Rich Client Task Logic

Rich Client and Online Differences

Operations - Colors