The Custom Actions feature in Valispace empowers both power users and normal users to create and apply custom automation scripts using Python and AI to enhance their project workflow. These custom actions can be linked to various objects within your project, such as components, requirements, or any other entities, and also can harness the capabilities of python and AI.
How can I Create Custom Actions?
Users can craft custom actions seamlessly within Valispace's scripting module, harnessing both scripting capabilities and AI functions. With this feature, users can effortlessly compose Python code in the scripting module's custom action and perform specific actions by leveraging the vali-assistant AI endpoint to generate the desired outputs through prompt or Python scripts.
Once a new Python script with the custom action is created within the scripting module, the users can create a custom action in the “General” option (1) within the script settings. The users must provide the object type information and description and fill in the “Display settings”, i.e. the display name and the position of the custom action.
In case the custom script is created to do a custom workflow in the components module, the user have to choose the “Placement” as components.
If the user creates a custom action script and doesnt provide the “Display Settings”, the custom action is not accessible for the user within the three dots menu. Each User have to create the Display Settings from the script to be able to show the “custom action” in the modules.
If the user have the minimum “Read only” access to the script, the user can create the custom action.
The user can also share the custom action with any of the user or group within the deployment using the “Share with” option underneath the display settings.
The Custom Actions overview is accessible in the "Settings" menu (1), allowing users to view the variety of custom actions (2) created by others. Users can seamlessly add or remove these actions from their display settings and customize their access to custom actions (3).
Custom Actions Workflows Examples:
Example 1: Convert the requirements Identifier from upper case to lower case
To demonstrate this example, we have already added the python script to the script templates within the module. The script converts the Identifiers Text from upper case to lower case. A quick video shows from how you can create a script, custom action and then how to use them in other modules.
The script has been added as a template within the scripting module. While creating a script, you can select “Custom actions” and then select the existing templates to reuse the code for your custom workflow as well.
Example 2: Translating the requirements from one language to another using the Valiassistant
Leveraging the ValiAssistant, you can effortlessly submit a set of requirements and instruct the vali-assistant, using a prompt, to translate them into any supported language of your choice.
Some other use cases that can be done with the custom actions
Quality check of a requirement
Create and add multiple valis to the component through component types
Check if the high level requirements are good and vice versa check if the low level requirements are not vague.
Suggest Requirement Type
Edit requirements text/formatting in bulk. eg: replace “must” with “shall etc.
Create summary of the requirements etc.
Note : These are possible scenarios that can be performed with the custom actions and there might be much more use cases that can be performed with the custom actions. If you have any scenarios that you would like to implement and if you need any help, please let us know and we can help you. You can reach out to us at firstname.lastname@example.org
Access to Custom Actions
These user-created custom actions can then be conveniently saved for universal access, allowing them to be effortlessly associated with a variety of objects, including requirements and values within Valispace. This means that when an everyday user needs to execute a custom action, they can simply choose it from the "Actions" menu of the object(requirements or components), eliminating the necessity to navigate to the scripting module or a Dashboard for execution.
The custom actions for components module can be accessed similarly. However, the user have to be in the List all of “Components”