Generate Case Number

Another option here would be to utilize a constant for the daily ID value, create a sub process that gets this information for each record.  Assuming you have a 'CreatedOn' timestamp for each record, the sub process can query the DB to see if any requests have been created in the same day.  If not, reset the constant to 1 and return that value.  If so, increment the constant and return the incremented value. 

Another option here would be to utilize a constant for the daily ID value, create a sub process that gets this information for each record.  Assuming you have a 'CreatedOn' timestamp for each record, the sub process can query the DB to see if any requests have been created in the same day.  If not, reset the constant to 1 and return that value.  If so, increment the constant and return the incremented value. 

Remember Appian saves previous versions of constants when they are changed.  This uses memory.
The constant approach suggested above is easy to build, but it may not scale well over time.

I'd use a variant of what Stewart Burchell recommends.

Hi Robert, to note in my experience Appian does not save a version to memory of a numeric constant that is incremented using the Increment Constant node so this is scalable.  Constant versions are saved during manual updates, or when a constant is modified using the Update Constant node. 

To add, for retaining scalability when resetting the constant I would recommend utilizing the Increment Constant node with a negative value (the negative value of the constant) to reset to 0, then perform the increment to get the first value (1) for the day, and no versions will be logged, vs using the Update Constant node to reset which would log a version each day. 

Not bad, Chris.  I am corrected.

So there's a small expression needed to obtain the value of the constant in order to properly reset it in this way.

I might do this next time.

Thanks!