While there are many native features available that could potentially meet your needs without the use of custom functions, we understand that custom functions may still be required in some cases. If the native features do not solve your issue, please provide a detailed use case and outline your attempts so far. This will help us avoid unnecessary probing and ensure we understand the scope of your request.
To build an effective custom function, we need the following details:
Detailed Use Case: A clear explanation of the problem you're trying to solve and how you'd like the custom function to behave.
API Considerations: Some APIs, like retrieving history, are not publicly available and may involve more API calls. Understanding your requirements in depth will help us decide the best approach and avoid inefficient API usage.
Custom Fields: If the custom function involves custom fields, please provide the field key.
Please note, we will always try to minimize the use of custom functions if the required feature is already available in a way or under development. Below is an example of how a custom function requirement gathering might look: (Prerequisites for Automating Child Request Creation from Parent Request)
Gather the following details from the user before involving our development team:
Number of child requests to be created (we allow between 3 to 5, with a maximum limit of 5).
Fields that should be copied from the original request template.
Values that need to be hard-coded in the new requests.
Template names for the child request templates.
If additional fields are involved, provide the field key for those fields.