@Miguel
Dear Miguel

After analysis, the problem is caused by an "&" in the group space name:
fa6dda8f-37b3-4da8-bdad-b6d83c1adf0f-image.png

This issue will be corrected in a future version. In the meantime, you can change the file name.

Kind regards,
Léa Angelloz

Dear @Miguel this functionality has been recorded in our system with number GOFAST-11620. Are roadmap is currently very dense so it is likely that we will wait for a customer to order it.

Kind regards,

Hello Miguel,
In your version of GoFAST and in later versions, this feature is not available. Once a task has been validated, it is not possible to go back and perform it again.
So that this type of functionality can be integrated into a new version of GoFAST, I have just created an internal JIRA under the reference “GOFAST-12127”.
In the meantime, I wish you a pleasant day,
Best regards,
Damien VANZO

Hello Miguel,
It is not possible to start a task from this menu.
In order to correct this problem in a future version, I've just created an internal jira under the reference “GOFAST-12126” so that this functionality will be available in a future version.

In the meantime, I wish you a pleasant day,
Best regards,
Damien VANZO

Dear @Miguel,

This feature is already possible through specific workflows. It must be designed into the specific workflow of the Bonita engine and the UI.

For the moment this feature isn't available for standard workflows.

Kind regards,

Ah thank you I understand better now!

Yes it's doesn't update neither when a process model is updated. Which is more problematic and closer to daily-basis use.

I created the issue GOFAST-12115 in our internal tracker to schedule a fix for this in an upcoming release.

Thank you for the feedback!

Raphaël.

Dear @Miguel, the community development seems to be on pause. Some of our customers are ordering that kind of developments so you could also if it is mandatory in the case of your projects.

Best regards,

Hello Miguel,

I hope you're fine. From what I understand it's a matter of workflow modelization.

Indeed you can run another workflow after a task as a subprocess, and the same way you can send data to the subprocess when initializing it, you can also receive data when the subprocess has ended. So it's possible to map this data to some control variables (e. g. a boolean is_ongoing which would be set to true when we receive some data when the subprocess ends, or a map of booleans { subprocess_id => is_ongoing }).

So in your workflow diagram right after the subprocess call you may create some kind of loop, like we go to a timer running every 5mn or so, after the timer has run we check whether the subprocess has finished : if the subprocess has finished we go to the next task, otherwise we loop back to the timer.

There may be other ways to achieve this, but this is what comes to my mind at first glance.

Best regards,
Raphaël.

Dear @Léa-Angelloz,

Sorry, the option to post a video is not available.

2105eb4b-e632-4e6d-97f0-c883cdf16a76-image.png

Kind regards,
Miguel SIMOES

@Miguel

Dear Miguel,

This problem will be corrected very quickly in version 4.3.0 R2.

Thanks

Kind regards,

Léa Angelloz

Hello @Miguel,

Yes I confirm that the scrollbar is disabled here, but you should be able to scroll in the tree anyway

Could you try it and get back to me ?

Thank you in advance !

Dear @Miguel, we have for now no other customer requesting it (yet) therefore it is not in the short term on the roadmap. We have a user club once a year (next one in the next few month) where we can bring this proposition up.
Best regards,
Christopher

@Miguel

Dear Miguel,

This is not planned for now because there's still a minor version scheduled before the next major release, but this new feature will be included in the next major version

Kind Regards,

Léa Angelloz

Dear @Léa-Angelloz,

Many thanks for the update.

Kind regards,
Miguel SIMOES

@Miguel

Dear Miguel,

No, currently it's not possible to change a workflow once it is already ongoing. However, I have created a Jira ticket to assess if it can be done (GOFAST-12082).

Kind regards,
Léa Angelloz

Dear @Léa-Angelloz,

Could you please inform us if there any development on this issue?

Thank you.

Kind regards,
Miguel SIMOES

Hello,

I should have been more accurate. The fix version for this is 4.3.0_R2, whose deployment is beginning this week.

Best regards,
Raphaël.

Dear @Miguel,

In GoFAST v4.3 (June 24), we will include a subset of SurveyJS webform designer, a demo can be found here https://surveyjs.io/survey-creator/examples/product-feedback-survey-template/reactjs#

Best,

Hello, it's really not a good idea to abruptly delete nodes from the database.

There are many reasons for this: it's impossible to restore them afterwards (e.g. if restoring from alfresco recycle bin from example), many of the database entries linked to the node will still remain in the database (e.g. the node fields) so it will be far away from "clean", and no hook (e.g. synchronization hooks with alfresco and element) will be triggered, which will generate even more inconsistencies. This is why GoFAST unpublishes nodes and, by design, never deletes them outright.

Best regards,
Raphaël.