Jump to content

Replacing the Request Details standard form: does it comprise just "h_summary" and "h_description"?


Berto2002
 Share

Recommended Posts

I have an issue with some Users writing really long Incident Summaries in the standard Request Details form. When the workflow gets to adding the Request to a Board as a Card, using the Summary as the Title, we get an error that there's a character limit. I could truncate at that stage but what it's revealed is that some users are writing long sentences in the Summary or pasting the Description into the Summary; so I want to stop that at source (logging).

In our standard Request flow, I have fixed this by entering a Regex validation to only allow 100 chars in the Summary: ^(?!(^-|-$|.{100,})).*

image.thumb.png.9425784af0e4a782de906e4057dce077.png

But our Incident flow was built using the standard Request Details form which we cannot configure:

image.png.95df9e0605c2618ded4437f64d57e7dd.png

When I view that form it looks like it is just two fields:

image.png.5ae3028ae2a82462d4404161179f88e3.png

So I want to replace the standard form with a custom form that does exactly the same thing but where I can input Regex. All I would like to know is to confirm the standard form comprises just "h_summary" and "h_description" and what is the FormID I should use since that is not listed for standard forms and is important for workflows. I intend to add a custom form with just those two fields (and the same FormID) so it does exactly the same without risk to my BPM?

Thank you.

Link to comment
Share on other sites

Hi @Berto2002

Yes it comprises of the two fields you mention - and your solution should be perfectly feasible. 

One thing to keep in mind though - the out-of-the-box Summary/Description form has also been built to work so that if a request is raised off the back of an email, the text in the Subject/Body of the email is populated into the Summary/Description of the form during the progressive capture. If this is something you would like to retain, then when creating the replacement Custom Form, ensure to get it the following Form ID:

customformdefaults

Then also make sure you map the two fields to h_summary, and h_description as you've described. And hopefully that should result in the desired replica which you can add your regex too.

Thanks

Bob

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...