Clarity: BPM: Process with update event for OBS start condition does not initiate.

Document ID : KB000050570
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

BPM: The process that is started based on the update events and contains the OBS start condition is not kicked off.

The reason is another definition of the process that is triggered by the update events. If there is no other process (in our case the ProcessUU) the process will be kicked off correctly.

Steps to Reproduce:

  1. Create a partition model

    1. Go to admin tools - Clarity studio - partition model

    2. Click the "new" button and enter requested information

    3. Go to the "Partitions" TAB and click the "New" button

    4. Create a two levels partition structure (Plevel1,Plevel2)

    5. Click the "properties" icon next to each level of partition and set up Partition Member - Resource

    6. Go to admin tools - Clarity studio -Object - "project" and set up the Partition model

    7. Log off and log on

  2. Create a OBS structure

    1. Go to admin tools - Organization and Access - OBS and click "New" button

    2. Create a two levels OBS structure (Olevel1,Olevel2) , click the "Save" button and Associate the project object (Associated Objects = project - Any Unit)

    3. Create a two levels OBS unit structure (Ouni1,Ounit2)

  3. Create a process "processC" based on the start create event

    1. Go to admin tools - Data administration - Processes

    2. Click the "New" button and enter requested information (Process Name = "processC")

    3. Go to Process Definition: Objects - and set up (Object Type = project, Partition = Upper level, Partition Association Mode = Partition, ancestors and descendants) click the "Save " button

    4. Go to Process start Options and set up (Start Option = "Auto-start", Start Event = "Create", Start Condition = project-obs = Ouni1)

    5. Go to Process Definition:Start Step - Post condition- Then Go To - Finish

    6. Go to Process Validation and click the "Validate All and Activate" button

  4. Create a process "processU" based on the start update event

    1. Go to admin tools - Data administration - Processes - "processC"

    2. Go to Process Definition and click "Save as" and enter requested information (rocess Name = "processC)

    3. Go to Process start Options and set up (Start Event = "Update")

    4. Go to Process Validation and click the "Validate All and Activate" button

  5. Create a process "processUU" based on the start update event

    1. Go to admin tools - Data administration - Processes - "processUU"

    2. Go to Process Definition and click "Save as" and enter requested information (rocess Name = "processUU)

    3. Go to Process start Options and set up (Start Event = "Update")

    4. Go to Start Condition - Set Condition - and set up (project.description__oldValue != project.description)

    5. Go to Process Validation and click the "Validate All and Activate" button

  6. Create a project a project "project_test"

    1. Go to Home - Portfolio Management - Projects and click the "New" button and choose partition click "Next"

    2. Enter requested information (Project Name = "project_test" ... Organizational Breakdown Structures - OBS - obs =Olevel1)

    3. Click Save

    4. Go to the "Processes" Tab- Initiated and check the initated processes (You should see kicked off "processC" process )

  7. Update the project "project_test"

    1. Go to the "Properties Tab " and change the "Description " attribute and click save

    2. Go to the "Processes" Tab- Initiated and check the initated processes (You should see kicked off two processes -"processC" and "processU")

Expected Result: The process "processU" should be kicked off as well as the processC and processUU
Actual Result: The process "processU" is not kicked off after project updating

Solution:

Workaround:
None.

Status/Resolution:
Resolved in Clarity 8.1.2 and beyond

Keywords: CLARITYKB, CLRT-20419, clarity8resolved.