App Builder

Would love the ability to customize the error page for people who are not authorized to view a page.

Allow to select "All current and future orgs" in app builder permissions on the "app" and on page level permission.

Support setting triggers for on page load workflows so integration override's can be used. So workflows trigger correctly for child orgs.

Rewst webhook responses cannot be read from the browser. Rewst's infrastructure does not seem to return Access-Control-Allow-Origin headers, even when configured in the webhook trigger settings. The browser, therefore, blocks the response, making it impossible to read workflow output from JavaScript.

Currently, the on form submit redirect only executes on workflow completion. We should have 2 separate options, 1 for on submit which should actually be on submit without any delay, and 1 on workflow completion.

Ability to choose for a page with a form loaded in a modal dialog to automatically close upon successful submission of the form.

Allow for the ai to be able to make the changes requested to ease the engineering curve of developing the app screens please.

I ran into an issue while trying to trigger a workflow from within an App Builder page. Specifically, I encountered a CORS error because the App Builder’s origin URL isn’t whitelisted for the preflight check at rewst.engine.io . I was able to implement a workaround, but it required a fair bit of custom scripting. One of the ROC techs pointed me in the right direction by suggesting I could trigger a workflow by updating a label field and simulating a button click using JavaScript/HTML queries on the page. This worked for triggering the workflow, but I still had trouble getting the resulting data back into the HTML display. To resolve this, I added a MutationObserver to watch a button object (used as the output holder). Once the workflow returned and the button’s text was updated with new data, the observer inserted that data into the appropriate HTML block and then disconnected itself. This approach works well enough, and does give a bug if you execute the workflow again before it finished giving both field the same value as the first data back. But having native support for this kind of interaction between workflows and embedded app content would be incredibly helpful!

I would like to be able to create a live dashboard of client status or tickets without having to hard code a refresh in order to get new data on the page so that these can be up on TVs.

It would be great if custom roles could be referenced through the rewst_get_user task and in the context CTX.user.roleIds. This would allow us to assign page permissions and redirect accordingly based on the users role in the pages themselves. At the moment its just the standard roles that are contained in both of these.