latest posts

Hi Andreia,

the fields I'm using are just used to demonstrate the difference between the "Last comment" and the business rule for getting the current comment.

You would simply use the business rule in the condition of the If operator.

It would be up to you where you use this. It could be generally in the OnSaving action globally, or in the saving trigger of the step.

I will be on vacation for the next two weeks, so I will be less active.


Best regards,
Daniel

HI Daniel,

I want to send a notification is someone enters a comment in that step.
I checked your post, so you are creating something like
- Technical FIeld that saves last comment
- Technical field that saves a new comment
- Use both fields as execution condition
- If different, an email is sent

I have some questions:
- Where are you configuring this action? Instance saving, etc? In the workflow or global actions?
- I don't want to send any notifications with emails that might happen due to path transition, only if in that step, someone enters a comment

Thank you

I didn't think of this option, but that's how ideas are born. :)


Depending on your version and whether you can execute SDKs you could download this:
2021
https://github.com/Daniel-Krueger/webcon_cclsactions/releases/tag/0.1
2022
https://github.com/Daniel-Krueger/webcon_cclsactions/releases/tag/0.2

It has an action to change the form type. Since I'm using the official SDK it is supported.

Then you could add a custom path and use mass actions.

Best regards,
Daniel

You gave me an idea. I could just start new instances on the basis of the current ones copying all data and atachments and than delete the old. Thanks,

I know. I read the article before posting. Thanks.

I think that changing WFD_DTYPEID in the database is definitely not a good idea ;)

also remember that even manually changing the form type using the "Change form type" action causes a new process to be started (from the first step only with the same WFD_ID)

https://community.webcon.com/posts/post/the-change-form-type-action/289/18

Hi Wojtek,

would it be an option to simply switch the names of the form types, so that the Ids could be kept and only configurations need /reports would need to be changed. This way you wouldn't need to update the instances.

If this isn't an option there's no way around testing even if someone here would give you an answers. You would be doing this at your own risk anyway. :)

I would create a copy of the database and restore it in a test environment or create a similar case in the test environment with a new worklfow.

Best regards,
Daniel

Hi,
If you want to save, you can use such a script: $("#SaveToolbarButton").trigger('click');
or you can use INVOKE MANU ACTION (if you want do some actions)

How can the simulation of the pressing menu button can be performed?

Hi Community,

for the reason of proper premissions managment I need to change the form type for 500+ instances. Obviously I would like to avoid manual work.
Do you have ANY idea if the 'change form type' can be somehow automated? I need to change form type X to Y, no diferentiation whatsoever.
Maybe some SQL? Changing WFD_DTYPEID in WFElements and WFHistoryElements will be enough?
What do you think?

Thanks in advance.

Wojtek