Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The following sections explain the minimal coding needed for the process.

Table of Contents

Setting Up the Ping-Pong Process in yuuvis® RAD

This process, which reads the answer to a question, is one of the smallest you can design.

...

  • Unzip the project file (see Requirements) to the Documents folder.
  • Start yuuvis® RAD designer.
    • Click Open.
    • Navigate to the folder where the scenario was unzipped. Select the .eoproj file and confirm the selection with Open.
    • Open Process models in the navigation tree of the project.
    • Copy Ping-Pong in the navigation tree by right-clicking and then pasting it into the Process model of your deployed project.
    • Deploy Ping-Pong to your system by right-clicking the process model and selecting Deploy
  • In a browser (Firefox, Chrome, or Edge), open yuuvis® RAD management-studio at <servername>/enaio/management and log in with your administrator account.
    • Go to Main menu > Processes.
    • In Process Management, select register Models.
    • In the In-tray on the left, select Ping-Pong.
    • Click the Actions menu on the right and select Move. Specify where in the Model groups to move to.
    • Click the Actions menu again and select Activate.
  • In a browser, open yuuvis® RAD client and select any object.
    • Click the Actions menu on the right. Under More actions, you will see Start mini-process Ping-Pong.
    • How to use the process see below

...

Creating a Process Model

Start yuuvis® RAD designer.

  • Open a project.
  • Right-click on Process models in the navigation tree and select New process model. Enter a name, here Ping-Pong, and a namespace, here Examples.
    Now you can begin to define your process model by configuring tasks in the working area (middle area) and defining the attributes for each artifact (area on the right). 
  • Define the general attributes of the process model:
    • For each language, enter a Name for starting the process. The Name is displayed in the client object actions menu in More actions.
    • Optional: enter a Description to be displayed in the Information for the action.
    • In the client view My processes, select a role for Initiators (those who can start the process) and Process owners (those who can monitor the process). Here, System-User-Role was used for the initiators and System-Admin-Role for the process owners.
    • Check Show start form to display the form after the start action in the client has been selected.
    • Check Process start with main object to display the start action for each object with Main object type = ' ' and Main object type = Any.
    • Set some Data fields, here we use:
      answer (string), set by supporter (ID-User/Group)
      question (string), set by requester(ID-User/Group)
      subject (string), set with object title from the start form script, see below.
    • Set Subject with {var:subject}.
    • Define Start form with a script.

      Figure 3: Start form design and preview


      Figure 4: Start form script

  • Set the 'ping' and 'pong' tasks in the work area.
    • Click the Work item tool in the application bar. Then left-click in the work area where you want to place and span the task shape, and release the mouse.
      Enter the Technical name, here ping, to be used in event scripts.
      Enter the Name, here Ping support: answer question, to be shown in the client Inbox list.
    • Repeat the last two steps for the 'Pong' task.
      Enter the Technical name, here pong.
      Enter the Name, here Pong answer: Read support message.
    • Connect the tasks by clicking the 'ping' task. Then move the cursor over the right edge of the task shape until a small rectangle appears. Click the rectangle, then move the to the pong-task shape and release.


      Figure 5: designer work area and general process attributes

  • Define Ping Task Attributes
    • Select the 'ping' task.


      Figure 6: designer work area with 'ping' task selected and its attributes displayed

    • Set Participant type to "Script-controlled", then write the BeforeStartActivity script to define the participant (performer).

      Code Block
      languagejs
      titleBeforeStartEvent Script
      // defined supporter becomes performer
      
      var newPerformer = new $.OrgObject();
      	newPerformer.id = $.variable('supporter').value;
      	$.activity('this').performers.push(newPerformer); 
      
      $.done();


...