Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LRDOCS-4954, Kaleo Forms #18

Conversation

rbohl
Copy link

@rbohl rbohl commented Jul 18, 2018

@natocesarrego
Copy link
Owner

Just started reviewing :)

:octocat: Sent from GH.

@liferay-continuous-integration-hu liferay-continuous-integration-hu merged commit 079465f into natocesarrego:master Aug 9, 2018
Copy link
Owner

@natocesarrego natocesarrego left a comment

Choose a reason for hiding this comment

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

Hey @rbohl,

This pull request is reviewed.

Thanks.

The task assignments of this workflow are as follows:

- Technician Claim: Assigned to the Spa Technician Role.
- Managerial Approval: Assigned to the Spa Manager Role.
Copy link
Owner

Choose a reason for hiding this comment

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

The Workflow tasks in the screenshot have the name slightly different from the names written here. In the screenshot, the names are Technician and Manager Approval.

Each applicable workflow node (the initial state and each task) appears in a row
with its associated form and a button that lets you assign a form. In the Spa
Order Workflow definition, there are four nodes that need forms: StartNode,
Technician Claim, Managerial Approval, and Final Order. Next you'll assign a
Copy link
Owner

Choose a reason for hiding this comment

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

The Workflow tasks in the following screenshot have the name slightly different from the names written here. In the screenshot, the names are Technician and Manager Approval.

- Next look at the available fields. In this stage of the workflow, you don't
need all the fields. Delete these fields from the form (mouse over
the field and click the delete
icon--![Delete](../../../images/icon-trash.png)):
Copy link
Owner

Choose a reason for hiding this comment

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

What are there the purpose of these hyphens?

If you don't need to change any field settings in the form, click *Save*. On the
next screen choose your new form by clicking on it. Now the workflow
definition's StartNode has a form associated with it.
You have three more fields to create using these steps.
Copy link
Owner

Choose a reason for hiding this comment

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

Actually, there are three more field sets or forms to be created. 🙂


- Approved
- Managerial Comments
For the Technician Claim workflow task. Follow the same procedure used
Copy link
Owner

Choose a reason for hiding this comment

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

On the screenshots, this Workflow task is named as Technician instead of Technician Claim. 🙂


[Kaleo Designer](/discover/portal/-/knowledge_base/7-0/kaleo-designer)

[Using Workflow](/discover/portal/-/knowledge_base/7-0/enabling-workflow)
Copy link
Owner

Choose a reason for hiding this comment

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

Using Workflow is the name of the article for 7.0, but this article was renamed to Activating Workflow for 7.1. 😉

@rbohl
Copy link
Author

rbohl commented Aug 9, 2018

Hi @natocesarrego , this article was significantly shortened during the review process and the specific example was removed. It looks like all your comments were addressed or became obsolete due to other parallel editing. I don't expect this to happen with other articles that you have in your queue, but I'll try to make you aware if something significant has been changed since I sent a pull request to you.

@natocesarrego
Copy link
Owner

Ok, @rbohl. Thanks!

The current scenario was an uncommon situation due to the deadlines to publish the documentations, let's work together to write/review the documentations in a more comfortable deadline. 🙂😉

Best.

@rbohl
Copy link
Author

rbohl commented Aug 16, 2018

Agreed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants