Skip to content

Conversation

@ozgeMendix
Copy link
Contributor

This is still a draft. It needs to be merged when WorkflowCommons v4.0.0 is released to the marketplace.

@ozgeMendix
Copy link
Contributor Author

We will release the module after Mx11.0.0 beta 2 is GA.

3. Views workflow progress in the **My Initiated Workflows** overview.
3. Make sure the correct user entity is set in the **App Settings**: open **App Settings** > **Workflows** tab and set **User entity** to *Administration.Account*.
4. For Workflow Commons v2.1.0 and above, you need to configure the state change microflows in the **App Settings**: open **App Settings** > **Workflows** tab to configure the following state change microflows:
4. For Workflow Commons v2.1.0 up to (but not including) v4.0.0, you need to configure the state change microflows in the **App Settings**: open **App Settings** > **Workflows** tab to configure the following state change microflows:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Yiyun333 Now there is a single page for all version of WFC combined with all version of MX and it's very confusing. Version numbers are everywhere. With MX 11 there will be a new WFC module that only works with Mx 11 (and up). Can't we have a WFC page that does not mentioned any previous (prior to MX 11) Mx and WFC version other than: "if you want to upgrade WFC from Mx 10 to 11 click here"?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not just here, but also further down.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@PaulJongenMx Sorry, I've missed this message.

Can't we have a WFC page that does not mentioned any previous (prior to MX 11) Mx and WFC version other than: "if you want to upgrade WFC from Mx 10 to 11 click here"?

Could you clarify this a bit more? Since we don't have a versioned Workflow Commons page (like our refguide and how-tos), I think it's still valuable to keep the version information. But indeed we need to structure the information better. I am not exactly sure what you mean by the above comment though. Please explain further. Thanks!

Copy link

@PaulJongenMx PaulJongenMx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1st review by Paul

Copy link

@PaulJongenMx PaulJongenMx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

completed 2nd review

Copy link

@PaulJongenMx PaulJongenMx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2nd review

@ozgeMendix
Copy link
Contributor Author

Hi @Yiyun333,
This PR is ready to review. But, it needs to be merged when WorkflowCommons v4.0.0 is released to the marketplace.

@Yiyun333
Copy link
Collaborator

Hi @Yiyun333, This PR is ready to review. But, it needs to be merged when WorkflowCommons v4.0.0 is released to the marketplace.

@ozgeMendix Thanks a lot for the efforts in updating this documentation. I might have misunderstood the release time. When do you plan to release WorkflowCommons v4.0.0? More specifically, after 11 beta 2 is released or after 11 GA is released?

@ozgeMendix
Copy link
Contributor Author

Hi @Yiyun333, This PR is ready to review. But, it needs to be merged when WorkflowCommons v4.0.0 is released to the marketplace.

@ozgeMendix Thanks a lot for the efforts in updating this documentation. I might have misunderstood the release time. When do you plan to release WorkflowCommons v4.0.0? More specifically, after 11 beta 2 is released or after 11 GA is released?

Thanks. We plan to release with 11 beta 2, so probably on Tuesday, 27th.

@Yiyun333 Yiyun333 marked this pull request as ready for review May 27, 2025 07:08
@Yiyun333
Copy link
Collaborator

Comment: This PR can be published when the feature is released. A more holistic and structural review of this whole doc will be done afterwards.

@MariaShaposhnikova MariaShaposhnikova merged commit 6b3090f into mendix:development May 28, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants