latest posts

In the form is visible, the info passes there, but probably to check the editability rules the definition on not being empty needs to be registered in the database.
It worked, thank you for your support!

ok now I understand :-)
when the your editability rule is executed, the value of the "Related task" field is probably still empty.

You need to do this using a form rule (example attached)

Hi Jack,

I've deleted the instance ID for de Parent.
The idea is to use that Related Task field.
I've attached my configuration

Hi Andreia,
I don't know if I understand correctly, but can you show how you created the editability rule?
Additionally, do you have to set the "related task" field (1) if you have "Parent ID" (2)? Maybe you can make a rule based on "Parent ID"

Hello all,

I have a process that can be started either from a Parent workflow or in the workflow, using a menu option (creating a sub-task).

In the start step, I have editability rules, if the user is creating a sub-task, some fields can be edited, but if the task has come from another process, those fields cannot be changed.
In the URL, I'm passing the ID when the user creates a sub-task to a field in order to use it as editability parameter. However, although the field has information on it, I'm not able to make the fields editable.

This is only working when I use instance from parent workflow. I cannot use this last option because this always come from another process and only when it's a subtask, the fields can be changed.

Do you have any ideas on why this is not working?

Hello!

Both resolutions work just fine, thank you very very much!

Best Regards,

Igor

Hi Igor,
the first condition looks OK.
But in the second one you have to compare the date with TODAY (I assume you have date and time in the "Dzień" field).

I haven't found a function in WEBCON that returns only the date from the datetime field. But you can make a workaround (screenshots)

Hello there :)

I have yet another problem, regarding the form validation. I've attached the rules that I've applied.
What I want to do is I want to block the occurence of choosing current day while it's after 9.00 A.M.
Otherwise If the day is <> than Today() then the result is TRUE, which means, you are able to go further.

Best Regards,

Igor

"it's a bit strange, because I had exactly the same error as YOU and when I turned off the visibility of the list in the workflow I'm starting from (not the one I'm trying to start), the error stopped showing up and I went to the selected page (also https://google.com :-) )"

Apologize - I misunderstood your previous post, was thinking about the target form. Bingo! There is an item list in the workflow I'm kicking the link off from, and when I turned off the visibility of this field, the link button started to work again properly.
People don't use this button that often, that's why I haven't connected the error with adding the item list to this form.

Thanks a lot for your help! Issue is not solved, but at least I know the culprit and can make a workaround.

"Nope, I tried https://google.com as a link to eliminate any form related issues."
it's a bit strange, because I had exactly the same error as YOU and when I turned off the visibility of the list in the workflow I'm starting from (not the one I'm trying to start), the error stopped showing up and I went to the selected page (also https://google.com :-) )
but I have a little different version, although the error is the same

anyway, a link in an HTML field seems easier ;)