In a board, we cannot configure the actions created using 'create' and 'delete branch'. Is there any way to do it?
Have you looked into the "Forms" functionality? If you add a card of type "Action", and then select the "forms" option it allows you to add items to a list using a form type setup. Also as an alternative to the form, a process can be created to add items to a list and that published to the dashboard.
For the delete functionality, while there is not an explicit option, you can create a boolean line item called "Delete" in a grid you have published, then create a process to delete if the boolean is checked, and publish that as an action on the grid.
Hope this helps. Screenshot below.
Jt
@pooja_n
You can't directly publish these on Boards. Instead go to Worksheets and create FORM based Actions. And then go back to Boards and Use FORM actions.
@Misbah
I am not sure I got this right, can you please elaborate?
Do you mean using the 'Configure Worksheet Actions' option to create a form?
If yes, how is it different from 'Configure Actions' option available in Boards?
Saurabh
@saurabh.raheja
Yes I meant to do it from Worksheets when this reply was posted. But this thread is few months old and NUX has changed since then.
Now you can create FORMS from Boards as well.
Hope that clarifies
Hi all, The Client ID and Client Secret are available, intended for uploading and downloading files. Could anyone advise how to use these credentials DIRECTLY to make API requests? Thank you!
I have A6 as the parent list and two sibling lists: A6.5 and A7. The A7 list includes an attribute that maps to A6.5. In the UX, the user will select A6.5 using a content selector, and the grid (dimensioned by A7) should display only the A7 items associated with that selected A6.5. Since the selector is a page context and…
A quick reminder of the Bulk Copy functionality. Bulk Copy allows you copy large volumes of data from one slice of a model to another in a single, optimised operation, instead of using formulas or imports. Use case: copy a version (RF1) into a prior year version (PY RF1) using a versions list to allow for year-on-year…
