-
Notifications
You must be signed in to change notification settings - Fork 2.4k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
How can I fill out url field with display_url in http redirect task of workflow,please? #14967
Comments
Maybe the ContentItem is not in the input try
If you are trying to redirect back to a form location. In OC 1.8 we have a new task that would allow you to redirect the user back to where the form was originated from. |
Hi MikeAlayek, |
Hi, {{ Workflow.ContentItem | display_url }} throw exception, Workflow.ContentItem is null |
Then What event are you using to start your workflow? |
I used Http Request Event to start my workflow. {{ Workflow.Input.ContentItem | display_url }} render nothing. |
I think that is what you are doing wrong. I think for ContentItem to exists, you'll need to add a content item event like Created, updated or published content |
If I want to use Http Request Event to start my workflow and want to ContentItem to exists, What should I do,please? |
What is the logic that you are trying to handle in workflow? |
I'll submit the form of the ContentItem display page to trigger workflow, then it redirect to {{ Workflow.Input.ContentItem | display_url }} in the last activity "http redirect task" of workflow. |
Your workflow doesn't seem to be initiated by content items, so there's no input inside. Can I take a look at your workflow page? I need to know more information to assist you. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Hi,
How can I fill out url field with display_url in http redirect task of workflow,please?
{{ Workflow.Input.ContentItem | display_url }} is not correct.
The text was updated successfully, but these errors were encountered: