Planning Analytics

The deprecation of the rich client tier on Planning Analytics on Cloud and upcoming end of support for Planning Analytics Local 2.0.9 on April 30, 2025, will remove support for TM1 Applications (commonly referred to as TM1 Contributor).  TM1 Applications is not included in the Planning Analytics Local 2.1 release that replaces 2.0.9.  The Plan asset type in Planning Analytics Workspace is the spiritual successor to TM1 Applications.  Like TM1 Applications, Plans layers workflow capabilities on top of existing TM1 models.  The Planning Analytics product team is making significant investment in Workspace Plans to provide workflow capabilities that are familiar to users of TM1 Applications.  These features include assignment of members from an approval or responsibility dimension, locking and unlocking slices of data, and execution of Turbo Integrator processes during submission, approval and rejection of tasks.  

TM1 Applications has not been universally adopted by Planning Analytics users.  However, it does simplify and accelerate the process of deploying and managing contribution type workflows in Planning Analytics.  Many Planning Analytics customers have implemented custom workflow within the TM1 model, using dimensions and cubes to track the workflow state, and TI processes to update the workflow, set user assignments, manage access to cubes and slices, and add comments.  I've attached a set of TI processes and documentation that demonstrate how workflow can be implemented directly in a the TM1 model without Workspace Plans or TM1 Applications.  This set of processes can be used in both TM1 v11 and v12 models to provide workflow capabilities similar to TM1 Applications.

I will be happy to respond in this post to questions and feedback regarding these processes. This includes request to implement enhancements and address issues with the TI processes.

------------------------------
Stuart King
Product Manager
IBM Planning Analytics
------------------------------

The deprecation of the rich client tier on Planning Analytics on Cloud and upcoming end of support for Planning Analytics Local 2.0.9 on April 30, 2025, will remove support for TM1 Applications (commonly referred to as TM1 Contributor).  TM1 Applications is not included in the Planning Analytics Local 2.1 release that replaces 2.0.9.  The Plan asset type in Planning Analytics Workspace is the spiritual successor to TM1 Applications.  Like TM1 Applications, Plans layers workflow capabilities on top of existing TM1 models.  The Planning Analytics product team is making significant investment in Workspace Plans to provide workflow capabilities that are familiar to users of TM1 Applications.  These features include assignment of members from an approval or responsibility dimension, locking and unlocking slices of data, and execution of Turbo Integrator processes during submission, approval and rejection of tasks.  

TM1 Applications has not been universally adopted by Planning Analytics users.  However, it does simplify and accelerate the process of deploying and managing contribution type workflows in Planning Analytics.  Many Planning Analytics customers have implemented custom workflow within the TM1 model, using dimensions and cubes to track the workflow state, and TI processes to update the workflow, set user assignments, manage access to cubes and slices, and add comments.  I've attached a set of TI processes and documentation that demonstrate how workflow can be implemented directly in a the TM1 model without Workspace Plans or TM1 Applications.  This set of processes can be used in both TM1 v11 and v12 models to provide workflow capabilities similar to TM1 Applications.

I will be happy to respond in this post to questions and feedback regarding these processes. This includes request to implement enhancements and address issues with the TI processes.

------------------------------
Stuart King
Product Manager
IBM Planning Analytics
------------------------------

Thank you very much Stuart.

One quick question. The TI "}wf_updatenodestate" has:

ExecuteProcess( '}WF_.LockUnlock', 'pWorkflow', pWorkflow, 'pNode', pNode, 'pLock', pLock );

I guess the . should be different as well as LockUnlock does not exist as a TI.

Without going into the details myself, is it }wf_lockunlocknode or }wf_lockunlockworkflow ?

The text in the Word doc contains:

The }WF_LockUnlock TI process I called from }WF_UpdateNodeState to adjust the lock state of the nodes

So I assume it's }wf_lockunlocknode ? The text would need to be slightly adjusted there.

Will play around more when time permits.

Best regards,

Wim

The deprecation of the rich client tier on Planning Analytics on Cloud and upcoming end of support for Planning Analytics Local 2.0.9 on April 30, 2025, will remove support for TM1 Applications (commonly referred to as TM1 Contributor).  TM1 Applications is not included in the Planning Analytics Local 2.1 release that replaces 2.0.9.  The Plan asset type in Planning Analytics Workspace is the spiritual successor to TM1 Applications.  Like TM1 Applications, Plans layers workflow capabilities on top of existing TM1 models.  The Planning Analytics product team is making significant investment in Workspace Plans to provide workflow capabilities that are familiar to users of TM1 Applications.  These features include assignment of members from an approval or responsibility dimension, locking and unlocking slices of data, and execution of Turbo Integrator processes during submission, approval and rejection of tasks.  

TM1 Applications has not been universally adopted by Planning Analytics users.  However, it does simplify and accelerate the process of deploying and managing contribution type workflows in Planning Analytics.  Many Planning Analytics customers have implemented custom workflow within the TM1 model, using dimensions and cubes to track the workflow state, and TI processes to update the workflow, set user assignments, manage access to cubes and slices, and add comments.  I've attached a set of TI processes and documentation that demonstrate how workflow can be implemented directly in a the TM1 model without Workspace Plans or TM1 Applications.  This set of processes can be used in both TM1 v11 and v12 models to provide workflow capabilities similar to TM1 Applications.

I will be happy to respond in this post to questions and feedback regarding these processes. This includes request to implement enhancements and address issues with the TI processes.

------------------------------
Stuart King
Product Manager
IBM Planning Analytics
------------------------------

Hi Wim,

Thanks for the quick feedback.  You are correct that it should be }WF_LockUnlockNode.  I'll update the processes and replace the attachment. 

I will also add a few important design details here: 

1 - The workflow processes do not strongly define node states.  The node state is updated with the }WF_UpdateNodeState process.  When you run this process, presumably from an action button in a PAW book or Websheet, you can use any string you want to update the state.  If you want to emulate TM1 Applications you would use the states listed here (e.g Available, Reserved, Locked, Incomplete, Ready).  As you implement these processes you will need to determine which states should lock or unlock the node.  

2 - There are two security modes, pSecurityMode parameter in the }WF_CreateWorkflow processs.  The Group security mode uses existing groups in TM1 just like TM1 Applications.  The Client security mode will allow you to name specific users (members in the }Clients dimension) as contributors and reviewers for each node.  When using the Client security the security groups will be created and applied automatically when the }WF_AssignNode process is used to make assignments.

3 - Locking slices is enforced with the GlobalSecurityOverlay mechanism in TM1, just like TM1 Applications.  However, I have two locking modes, Any and All.  The Any mode means that any user or group that attempts to lock the node when using the }WF_UpdateNodeState process will cause the node to be locked for all contributors assigned to the node.  The All locking mode will prevent the node from being locked until all users or groups assigned to the node have used the }WF_UpdateNodeState process to lock the node.

Thank you very much Stuart.

One quick question. The TI "}wf_updatenodestate" has:

ExecuteProcess( '}WF_.LockUnlock', 'pWorkflow', pWorkflow, 'pNode', pNode, 'pLock', pLock );

I guess the . should be different as well as LockUnlock does not exist as a TI.

Without going into the details myself, is it }wf_lockunlocknode or }wf_lockunlockworkflow ?

The text in the Word doc contains:

The }WF_LockUnlock TI process I called from }WF_UpdateNodeState to adjust the lock state of the nodes

So I assume it's }wf_lockunlocknode ? The text would need to be slightly adjusted there.

Will play around more when time permits.

Best regards,

Wim

The deprecation of the rich client tier on Planning Analytics on Cloud and upcoming end of support for Planning Analytics Local 2.0.9 on April 30, 2025, will remove support for TM1 Applications (commonly referred to as TM1 Contributor).  TM1 Applications is not included in the Planning Analytics Local 2.1 release that replaces 2.0.9.  The Plan asset type in Planning Analytics Workspace is the spiritual successor to TM1 Applications.  Like TM1 Applications, Plans layers workflow capabilities on top of existing TM1 models.  The Planning Analytics product team is making significant investment in Workspace Plans to provide workflow capabilities that are familiar to users of TM1 Applications.  These features include assignment of members from an approval or responsibility dimension, locking and unlocking slices of data, and execution of Turbo Integrator processes during submission, approval and rejection of tasks.  

TM1 Applications has not been universally adopted by Planning Analytics users.  However, it does simplify and accelerate the process of deploying and managing contribution type workflows in Planning Analytics.  Many Planning Analytics customers have implemented custom workflow within the TM1 model, using dimensions and cubes to track the workflow state, and TI processes to update the workflow, set user assignments, manage access to cubes and slices, and add comments.  I've attached a set of TI processes and documentation that demonstrate how workflow can be implemented directly in a the TM1 model without Workspace Plans or TM1 Applications.  This set of processes can be used in both TM1 v11 and v12 models to provide workflow capabilities similar to TM1 Applications.

I will be happy to respond in this post to questions and feedback regarding these processes. This includes request to implement enhancements and address issues with the TI processes.

------------------------------
Stuart King
Product Manager
IBM Planning Analytics
------------------------------

Hi Stuart,

This is looking good. Were you going to include a sample Websheet? I did not see it embedded in the Word Document or in the zip file.

Hi Wim,

Thanks for the quick feedback.  You are correct that it should be }WF_LockUnlockNode.  I'll update the processes and replace the attachment. 

I will also add a few important design details here: 

1 - The workflow processes do not strongly define node states.  The node state is updated with the }WF_UpdateNodeState process.  When you run this process, presumably from an action button in a PAW book or Websheet, you can use any string you want to update the state.  If you want to emulate TM1 Applications you would use the states listed here (e.g Available, Reserved, Locked, Incomplete, Ready).  As you implement these processes you will need to determine which states should lock or unlock the node.  

2 - There are two security modes, pSecurityMode parameter in the }WF_CreateWorkflow processs.  The Group security mode uses existing groups in TM1 just like TM1 Applications.  The Client security mode will allow you to name specific users (members in the }Clients dimension) as contributors and reviewers for each node.  When using the Client security the security groups will be created and applied automatically when the }WF_AssignNode process is used to make assignments.

3 - Locking slices is enforced with the GlobalSecurityOverlay mechanism in TM1, just like TM1 Applications.  However, I have two locking modes, Any and All.  The Any mode means that any user or group that attempts to lock the node when using the }WF_UpdateNodeState process will cause the node to be locked for all contributors assigned to the node.  The All locking mode will prevent the node from being locked until all users or groups assigned to the node have used the }WF_UpdateNodeState process to lock the node.

Thank you very much Stuart.

One quick question. The TI "}wf_updatenodestate" has:

ExecuteProcess( '}WF_.LockUnlock', 'pWorkflow', pWorkflow, 'pNode', pNode, 'pLock', pLock );

I guess the . should be different as well as LockUnlock does not exist as a TI.

Without going into the details myself, is it }wf_lockunlocknode or }wf_lockunlockworkflow ?

The text in the Word doc contains:

The }WF_LockUnlock TI process I called from }WF_UpdateNodeState to adjust the lock state of the nodes

So I assume it's }wf_lockunlocknode ? The text would need to be slightly adjusted there.

Will play around more when time permits.

Best regards,

Wim

The deprecation of the rich client tier on Planning Analytics on Cloud and upcoming end of support for Planning Analytics Local 2.0.9 on April 30, 2025, will remove support for TM1 Applications (commonly referred to as TM1 Contributor).  TM1 Applications is not included in the Planning Analytics Local 2.1 release that replaces 2.0.9.  The Plan asset type in Planning Analytics Workspace is the spiritual successor to TM1 Applications.  Like TM1 Applications, Plans layers workflow capabilities on top of existing TM1 models.  The Planning Analytics product team is making significant investment in Workspace Plans to provide workflow capabilities that are familiar to users of TM1 Applications.  These features include assignment of members from an approval or responsibility dimension, locking and unlocking slices of data, and execution of Turbo Integrator processes during submission, approval and rejection of tasks.  

TM1 Applications has not been universally adopted by Planning Analytics users.  However, it does simplify and accelerate the process of deploying and managing contribution type workflows in Planning Analytics.  Many Planning Analytics customers have implemented custom workflow within the TM1 model, using dimensions and cubes to track the workflow state, and TI processes to update the workflow, set user assignments, manage access to cubes and slices, and add comments.  I've attached a set of TI processes and documentation that demonstrate how workflow can be implemented directly in a the TM1 model without Workspace Plans or TM1 Applications.  This set of processes can be used in both TM1 v11 and v12 models to provide workflow capabilities similar to TM1 Applications.

I will be happy to respond in this post to questions and feedback regarding these processes. This includes request to implement enhancements and address issues with the TI processes.

------------------------------
Stuart King
Product Manager
IBM Planning Analytics
------------------------------

Hi Wim,

Thanks for the quick feedback.  You are correct that it should be }WF_LockUnlockNode.  I'll update the processes and replace the attachment. 

I will also add a few important design details here: 

1 - The workflow processes do not strongly define node states.  The node state is updated with the }WF_UpdateNodeState process.  When you run this process, presumably from an action button in a PAW book or Websheet, you can use any string you want to update the state.  If you want to emulate TM1 Applications you would use the states listed here (e.g Available, Reserved, Locked, Incomplete, Ready).  As you implement these processes you will need to determine which states should lock or unlock the node.  

2 - There are two security modes, pSecurityMode parameter in the }WF_CreateWorkflow processs.  The Group security mode uses existing groups in TM1 just like TM1 Applications.  The Client security mode will allow you to name specific users (members in the }Clients dimension) as contributors and reviewers for each node.  When using the Client security the security groups will be created and applied automatically when the }WF_AssignNode process is used to make assignments.

3 - Locking slices is enforced with the GlobalSecurityOverlay mechanism in TM1, just like TM1 Applications.  However, I have two locking modes, Any and All.  The Any mode means that any user or group that attempts to lock the node when using the }WF_UpdateNodeState process will cause the node to be locked for all contributors assigned to the node.  The All locking mode will prevent the node from being locked until all users or groups assigned to the node have used the }WF_UpdateNodeState process to lock the node.

------------------------------
Stuart King
Product Manager
IBM Planning Analytics

Original Message:
Sent: Tue July 30, 2024 06:20 AM
From: Wim Gielis
Subject: TM1 Model Based Workflow (deprecation of TM1 Applications)

Thank you very much Stuart.

One quick question. The TI "}wf_updatenodestate" has:

ExecuteProcess( '}WF_.LockUnlock', 'pWorkflow', pWorkflow, 'pNode', pNode, 'pLock', pLock );

I guess the . should be different as well as LockUnlock does not exist as a TI.

Without going into the details myself, is it }wf_lockunlocknode or }wf_lockunlockworkflow ?

The text in the Word doc contains:

The }WF_LockUnlock TI process I called from }WF_UpdateNodeState to adjust the lock state of the nodes

So I assume it's }wf_lockunlocknode ? The text would need to be slightly adjusted there.

Will play around more when time permits.

Best regards,

Wim

------------------------------
Wim Gielis

Original Message:
Sent: Mon July 29, 2024 11:41 PM
From: STUART KING
Subject: TM1 Model Based Workflow (deprecation of TM1 Applications)

The deprecation of the rich client tier on Planning Analytics on Cloud and upcoming end of support for Planning Analytics Local 2.0.9 on April 30, 2025, will remove support for TM1 Applications (commonly referred to as TM1 Contributor).  TM1 Applications is not included in the Planning Analytics Local 2.1 release that replaces 2.0.9.  The Plan asset type in Planning Analytics Workspace is the spiritual successor to TM1 Applications.  Like TM1 Applications, Plans layers workflow capabilities on top of existing TM1 models.  The Planning Analytics product team is making significant investment in Workspace Plans to provide workflow capabilities that are familiar to users of TM1 Applications.  These features include assignment of members from an approval or responsibility dimension, locking and unlocking slices of data, and execution of Turbo Integrator processes during submission, approval and rejection of tasks.  

TM1 Applications has not been universally adopted by Planning Analytics users.  However, it does simplify and accelerate the process of deploying and managing contribution type workflows in Planning Analytics.  Many Planning Analytics customers have implemented custom workflow within the TM1 model, using dimensions and cubes to track the workflow state, and TI processes to update the workflow, set user assignments, manage access to cubes and slices, and add comments.  I've attached a set of TI processes and documentation that demonstrate how workflow can be implemented directly in a the TM1 model without Workspace Plans or TM1 Applications.  This set of processes can be used in both TM1 v11 and v12 models to provide workflow capabilities similar to TM1 Applications.

I will be happy to respond in this post to questions and feedback regarding these processes. This includes request to implement enhancements and address issues with the TI processes.

------------------------------
Stuart King
Product Manager
IBM Planning Analytics
------------------------------

Do we need to run '}tp_admin_delete_all' before utilizing this package. I could not wind the websheet in package.

Hi Wim,

Thanks for the quick feedback.  You are correct that it should be }WF_LockUnlockNode.  I'll update the processes and replace the attachment. 

I will also add a few important design details here: 

1 - The workflow processes do not strongly define node states.  The node state is updated with the }WF_UpdateNodeState process.  When you run this process, presumably from an action button in a PAW book or Websheet, you can use any string you want to update the state.  If you want to emulate TM1 Applications you would use the states listed here (e.g Available, Reserved, Locked, Incomplete, Ready).  As you implement these processes you will need to determine which states should lock or unlock the node.  

2 - There are two security modes, pSecurityMode parameter in the }WF_CreateWorkflow processs.  The Group security mode uses existing groups in TM1 just like TM1 Applications.  The Client security mode will allow you to name specific users (members in the }Clients dimension) as contributors and reviewers for each node.  When using the Client security the security groups will be created and applied automatically when the }WF_AssignNode process is used to make assignments.

3 - Locking slices is enforced with the GlobalSecurityOverlay mechanism in TM1, just like TM1 Applications.  However, I have two locking modes, Any and All.  The Any mode means that any user or group that attempts to lock the node when using the }WF_UpdateNodeState process will cause the node to be locked for all contributors assigned to the node.  The All locking mode will prevent the node from being locked until all users or groups assigned to the node have used the }WF_UpdateNodeState process to lock the node.

Thank you very much Stuart.

One quick question. The TI "}wf_updatenodestate" has:

ExecuteProcess( '}WF_.LockUnlock', 'pWorkflow', pWorkflow, 'pNode', pNode, 'pLock', pLock );

I guess the . should be different as well as LockUnlock does not exist as a TI.

Without going into the details myself, is it }wf_lockunlocknode or }wf_lockunlockworkflow ?

The text in the Word doc contains:

The }WF_LockUnlock TI process I called from }WF_UpdateNodeState to adjust the lock state of the nodes

So I assume it's }wf_lockunlocknode ? The text would need to be slightly adjusted there.

Will play around more when time permits.

Best regards,

Wim

The deprecation of the rich client tier on Planning Analytics on Cloud and upcoming end of support for Planning Analytics Local 2.0.9 on April 30, 2025, will remove support for TM1 Applications (commonly referred to as TM1 Contributor).  TM1 Applications is not included in the Planning Analytics Local 2.1 release that replaces 2.0.9.  The Plan asset type in Planning Analytics Workspace is the spiritual successor to TM1 Applications.  Like TM1 Applications, Plans layers workflow capabilities on top of existing TM1 models.  The Planning Analytics product team is making significant investment in Workspace Plans to provide workflow capabilities that are familiar to users of TM1 Applications.  These features include assignment of members from an approval or responsibility dimension, locking and unlocking slices of data, and execution of Turbo Integrator processes during submission, approval and rejection of tasks.  

TM1 Applications has not been universally adopted by Planning Analytics users.  However, it does simplify and accelerate the process of deploying and managing contribution type workflows in Planning Analytics.  Many Planning Analytics customers have implemented custom workflow within the TM1 model, using dimensions and cubes to track the workflow state, and TI processes to update the workflow, set user assignments, manage access to cubes and slices, and add comments.  I've attached a set of TI processes and documentation that demonstrate how workflow can be implemented directly in a the TM1 model without Workspace Plans or TM1 Applications.  This set of processes can be used in both TM1 v11 and v12 models to provide workflow capabilities similar to TM1 Applications.

I will be happy to respond in this post to questions and feedback regarding these processes. This includes request to implement enhancements and address issues with the TI processes.

------------------------------
Stuart King
Product Manager
IBM Planning Analytics
------------------------------

Do we need to run '}tp_admin_delete_all' before utilizing this package. I could not wind the websheet in package.

Hi Wim,

Thanks for the quick feedback.  You are correct that it should be }WF_LockUnlockNode.  I'll update the processes and replace the attachment. 

I will also add a few important design details here: 

1 - The workflow processes do not strongly define node states.  The node state is updated with the }WF_UpdateNodeState process.  When you run this process, presumably from an action button in a PAW book or Websheet, you can use any string you want to update the state.  If you want to emulate TM1 Applications you would use the states listed here (e.g Available, Reserved, Locked, Incomplete, Ready).  As you implement these processes you will need to determine which states should lock or unlock the node.  

2 - There are two security modes, pSecurityMode parameter in the }WF_CreateWorkflow processs.  The Group security mode uses existing groups in TM1 just like TM1 Applications.  The Client security mode will allow you to name specific users (members in the }Clients dimension) as contributors and reviewers for each node.  When using the Client security the security groups will be created and applied automatically when the }WF_AssignNode process is used to make assignments.

3 - Locking slices is enforced with the GlobalSecurityOverlay mechanism in TM1, just like TM1 Applications.  However, I have two locking modes, Any and All.  The Any mode means that any user or group that attempts to lock the node when using the }WF_UpdateNodeState process will cause the node to be locked for all contributors assigned to the node.  The All locking mode will prevent the node from being locked until all users or groups assigned to the node have used the }WF_UpdateNodeState process to lock the node.

Thank you very much Stuart.

One quick question. The TI "}wf_updatenodestate" has:

ExecuteProcess( '}WF_.LockUnlock', 'pWorkflow', pWorkflow, 'pNode', pNode, 'pLock', pLock );

I guess the . should be different as well as LockUnlock does not exist as a TI.

Without going into the details myself, is it }wf_lockunlocknode or }wf_lockunlockworkflow ?

The text in the Word doc contains:

The }WF_LockUnlock TI process I called from }WF_UpdateNodeState to adjust the lock state of the nodes

So I assume it's }wf_lockunlocknode ? The text would need to be slightly adjusted there.

Will play around more when time permits.

Best regards,

Wim

The deprecation of the rich client tier on Planning Analytics on Cloud and upcoming end of support for Planning Analytics Local 2.0.9 on April 30, 2025, will remove support for TM1 Applications (commonly referred to as TM1 Contributor).  TM1 Applications is not included in the Planning Analytics Local 2.1 release that replaces 2.0.9.  The Plan asset type in Planning Analytics Workspace is the spiritual successor to TM1 Applications.  Like TM1 Applications, Plans layers workflow capabilities on top of existing TM1 models.  The Planning Analytics product team is making significant investment in Workspace Plans to provide workflow capabilities that are familiar to users of TM1 Applications.  These features include assignment of members from an approval or responsibility dimension, locking and unlocking slices of data, and execution of Turbo Integrator processes during submission, approval and rejection of tasks.  

TM1 Applications has not been universally adopted by Planning Analytics users.  However, it does simplify and accelerate the process of deploying and managing contribution type workflows in Planning Analytics.  Many Planning Analytics customers have implemented custom workflow within the TM1 model, using dimensions and cubes to track the workflow state, and TI processes to update the workflow, set user assignments, manage access to cubes and slices, and add comments.  I've attached a set of TI processes and documentation that demonstrate how workflow can be implemented directly in a the TM1 model without Workspace Plans or TM1 Applications.  This set of processes can be used in both TM1 v11 and v12 models to provide workflow capabilities similar to TM1 Applications.

I will be happy to respond in this post to questions and feedback regarding these processes. This includes request to implement enhancements and address issues with the TI processes.

------------------------------
Stuart King
Product Manager
IBM Planning Analytics
------------------------------

Hi Wim,

Thanks for the quick feedback.  You are correct that it should be }WF_LockUnlockNode.  I'll update the processes and replace the attachment. 

I will also add a few important design details here: 

1 - The workflow processes do not strongly define node states.  The node state is updated with the }WF_UpdateNodeState process.  When you run this process, presumably from an action button in a PAW book or Websheet, you can use any string you want to update the state.  If you want to emulate TM1 Applications you would use the states listed here (e.g Available, Reserved, Locked, Incomplete, Ready).  As you implement these processes you will need to determine which states should lock or unlock the node.  

2 - There are two security modes, pSecurityMode parameter in the }WF_CreateWorkflow processs.  The Group security mode uses existing groups in TM1 just like TM1 Applications.  The Client security mode will allow you to name specific users (members in the }Clients dimension) as contributors and reviewers for each node.  When using the Client security the security groups will be created and applied automatically when the }WF_AssignNode process is used to make assignments.

3 - Locking slices is enforced with the GlobalSecurityOverlay mechanism in TM1, just like TM1 Applications.  However, I have two locking modes, Any and All.  The Any mode means that any user or group that attempts to lock the node when using the }WF_UpdateNodeState process will cause the node to be locked for all contributors assigned to the node.  The All locking mode will prevent the node from being locked until all users or groups assigned to the node have used the }WF_UpdateNodeState process to lock the node.

Thank you very much Stuart.

One quick question. The TI "}wf_updatenodestate" has:

ExecuteProcess( '}WF_.LockUnlock', 'pWorkflow', pWorkflow, 'pNode', pNode, 'pLock', pLock );

I guess the . should be different as well as LockUnlock does not exist as a TI.

Without going into the details myself, is it }wf_lockunlocknode or }wf_lockunlockworkflow ?

The text in the Word doc contains:

The }WF_LockUnlock TI process I called from }WF_UpdateNodeState to adjust the lock state of the nodes

So I assume it's }wf_lockunlocknode ? The text would need to be slightly adjusted there.

Will play around more when time permits.

Best regards,

Wim

The deprecation of the rich client tier on Planning Analytics on Cloud and upcoming end of support for Planning Analytics Local 2.0.9 on April 30, 2025, will remove support for TM1 Applications (commonly referred to as TM1 Contributor).  TM1 Applications is not included in the Planning Analytics Local 2.1 release that replaces 2.0.9.  The Plan asset type in Planning Analytics Workspace is the spiritual successor to TM1 Applications.  Like TM1 Applications, Plans layers workflow capabilities on top of existing TM1 models.  The Planning Analytics product team is making significant investment in Workspace Plans to provide workflow capabilities that are familiar to users of TM1 Applications.  These features include assignment of members from an approval or responsibility dimension, locking and unlocking slices of data, and execution of Turbo Integrator processes during submission, approval and rejection of tasks.  

TM1 Applications has not been universally adopted by Planning Analytics users.  However, it does simplify and accelerate the process of deploying and managing contribution type workflows in Planning Analytics.  Many Planning Analytics customers have implemented custom workflow within the TM1 model, using dimensions and cubes to track the workflow state, and TI processes to update the workflow, set user assignments, manage access to cubes and slices, and add comments.  I've attached a set of TI processes and documentation that demonstrate how workflow can be implemented directly in a the TM1 model without Workspace Plans or TM1 Applications.  This set of processes can be used in both TM1 v11 and v12 models to provide workflow capabilities similar to TM1 Applications.

I will be happy to respond in this post to questions and feedback regarding these processes. This includes request to implement enhancements and address issues with the TI processes.

------------------------------
Stuart King
Product Manager
IBM Planning Analytics
------------------------------

Regards.

Hi Jose,

Appreciate you pointing this out.  I've already made the changes to correct the issue.  I will do a bit more testing and upload a new version of the processes shortly.

Regards.

Hi, Stuart,

I was my understanding that the approval hierarchy piece related to TM1 Applications would be included in the 2.0.98 release of Workspace.  I am unable to locate it.  Did this piece not make it into 2.0.98 or is there something that needs to be configured for this to appear?

Hi Jose,

Appreciate you pointing this out.  I've already made the changes to correct the issue.  I will do a bit more testing and upload a new version of the processes shortly.

Regards.

Hi Jose,

Appreciate you pointing this out.  I've already made the changes to correct the issue.  I will do a bit more testing and upload a new version of the processes shortly.

Regards.

Hi Stuart,

First, thank you for sharing the code/websheet and documentation.   We have several customers that are looking at these resources to jump start a transition away from Contributor. 

I've been working with the code you shared above and have a question.  If we use Group as the Security Mode and a user runs the  }WF_UpdateNodeState TI process, the process errors out because, on line 29, it tries to use the user to update the state but the }WF_workflowname_State cube uses the }Groups dimension not the }Clients dimension (when built from }WF_CreateWorkflow).  I'm wondering if you ran into this and have updated code that you mention in your post? 

Obviously, we can enhance the TI processes to write to the cube using the }Client or the appropriate }Groups (if the user is a member of that group) but wanted to keep in sync with your shared solution if possible. 

Thanks,

Chris Wolfe 

Converge Technology Solutions

Hi Jose,

Appreciate you pointing this out.  I've already made the changes to correct the issue.  I will do a bit more testing and upload a new version of the processes shortly.

Regards.