Process Naming Convention Date Format remove Time

Follow

Valerie Westres

• January 25, 2019 16:23

I need to remove the Time from the Process Naming Convention when using a Date field.

I tried using Form Data Date fields, with format 'dd mmm yyyy'; however, that gets completely ignored on Naming Convention... any suggestions please?

0

• 

  Lucas Drege

  • January 25, 2019 20:50
  • Edited

  Valerie,

  I have an update for you.  In the latest version of the product, we have a checkbox item that can assist you, but comes with a caveat.

   

  

  A few things to think about with this approach:

  1. This configuration will remove the time and time zone component, so if any other elements of your process design needs that value, it will be lost.

  2. We cannot have 2 process instances with the same name, so without appending a guid/other unique identifier, only 1 such process instance can exist per day.

   

  Can you let me know which version of the product you're currently using?

  Lucas

  0

  Permalink
• 

  Valerie Westres

  • February 21, 2019 18:40

  Hi Lucas,

  I am on NX 6.0 SP1 SU2 Hotfix 4

  

  Please advise,

  0

  Permalink
• 

  Loren Bratzler

  • February 22, 2019 16:32

  Lucas - I have always wondered why AgilePoint requires that Process Instance Names must be unique?  The Primary Key to the WF_PROC_INSTS table is the Process Instance ID so it doesn't seem like it is a database restraint.

  1

  Permalink
• 

  Lucas Drege

  • February 22, 2019 22:57

  Loren, 

  The reason we have required unique process instance names is because it could cause confusion in things like the reporting module or in the workcenter.

  Lucas

  0

  Permalink
• 

  Loren Bratzler

  • March 01, 2019 20:00

  Lucas,

  You stated above that you can only have like-named process instances once per day.  I actually believe that you can only have like-named process instances once per Process Model version.

  I set up a simple process to test Process Instance Names.  The process consists of one Start task where you key a value into a Text Box and submit.  The process Naming Convention then takes the value of the text box and uses it for the Process Instance name:

  

  I then ran tests where I submitted the process multiple times.  I ran a process named "FIRST TEST" on 2/28 and then submitted a second one immediately after with the same value.  The second one used the default naming convention.  I then ran a third one named "SECOND TEST" and that one used my textbox value for the name.

  Then the next day, on 3/1, I submitted "FIRST TEST" and "SECOND TEST" again and those also got the default naming.

  It wasn't until I published a new version (version 1.01) that it would allow me to submit a process with the same name as a previous instance.

  

  0

  Permalink
• 

  Loren Bratzler

  • March 01, 2019 20:06
  • Edited

  One thing I would suggest to Valerie would be to try to use some other field values from your process in the naming convention to ensure the process instance name is unique.  The process you showed in your post appears to be a Time Off Request.  Perhaps you can add the requester's name to your naming convention and maybe combine that with the date that they are requesting off.

  0

  Permalink

Please sign in to leave a comment.