Show Ortems possibilities in collaborative mode in a plan:
- Planner user performs an action => how is it seen from Collaborator and Viewer sides.
- Collaborator user performs an action => how is it seen from Planner and Viewer sides.
- How to configure a Viewer user on auto-refresh mode in order that there is no action to perform to get the new up-to-date Work In Progress (WIP)
Usage
When plan will be automatically refreshed for the viewer once the settings are correct?
- When Planner user saves WIP or When a Collaborative user confirms its modifications
and
- When the Viewer user has switched its own “Apply pending events automatically” to “ON” in the status bar of its Planning module window. This action is very easy to perform. Locate in the status bar, the following icon: (when the automatic mode is ON) or (when the mode is OFF). Clicking on this icon will switch the mode.
Information for technical people about this automatic mode for Viewer users: the ON/OFF status for this mode is saved in the user desktop. In the database, the table name is BUREAU_FICHIER, the record is stored on NOM_FICHIER=’Win’ row, it relates to the concerned desktop (NOM_BUREAU=’ORT’ selects the default desktop), for the user (PROP_BUREAU=‘VIEWER’ selects the user ‘VIEWER’). The blob field containing the data is ‘CONTENU_FICHIER’. When activated, the ‘[Affichage]’ chapter into this field contains ‘APPLICATION_EVT_AUTO=1’.
Configuration
What to configure:
2 advanced parameters have to be set: DISPLAY_EVENT_ALERT and WIP_VALIDITY_CHECK.
- DISPLAY_EVENT_ALERT is a 0/1 data field that must be set to 1 (instead of 0)
- WIP_VALIDITY_CHECK is the duration in seconds between each scan for new WIP or new collaborative events (modifications confirmed by the user). Take care that:
- if value = 0, there is not scan
- if value >=1 and <=5, the value is considered as 5 (to avoid too frequently requests sent to the DB by each Viewer user)
- if value >=5, it represents the duration in seconds between each scan.
How to configure:
Since those settings are advanced, you can set them 2 different ways:
- through Vic IBU on table BUSINESS_CONFIG: manually in Table tab or using the following SQL update commands (sets to 30 seconds the duration between 2 check stages):
update BUSINESS_CONFIG set PARAM_VALUE='1' where PARAM_ID='DISPLAY_EVENT_ALERT';
update BUSINESS_CONFIG set PARAM_VALUE='30' where PARAM_ID='WIP_VALIDITY_CHECK';
or
- using “Options > Advanced configuration…” menu from Planning module (but additional settings may be required to allow modifications for these settings as explained in Q&As)
Here is a short query to check the values for those parameters:
select * from BUSINESS_CONFIG where PARAM_ID in ('DISPLAY_EVENT_ALERT','WIP_VALIDITY_CHECK')
Prerequisites
All along this document, it is written “Viewer profile users” where it is actually a Viewer profile assigned to an environment for a user. But in most of the cases, when a user is viewer on an environment, he is viewer on all the environments he’s allowed to access. That’s why the Viewer profile concept is often extended to the user, even though the configuration as viewer must be set on the environment. Here are the steps to follow:
To be viewer on an environment, the user must be assigned with a class whose “Profile” is “V”. To be done or checked: launch “Environment/User Management” module and go to “Users” tab. Then focus on the right part of the window. The Class column is the place where a V profile class must be assigned.
In standard installation, 2 classes are existing: “W – Viewing” and “STD_V – Viewer with full profile rights”.
