Initial Work status not set autmoatically for new created member

Question

Hi,
if we create a new budget version, and process the category dimension we notice that the first work status (locked in our scenario) is not set automatically by default... As a result users can still input data for the new budget version. Only if we first change the work status of the new budget version (and put it back), the work status can be applied ...
Is this normal behavior?
Dries

Answer 1

Yes, I think what you're seeing is "normal" behavior -- it may not be what you want, though. In fact, I don't think this issue is limited to your creating a new member. It also applies to the existing members of your work status dimensions.
I had one project like this, where the customer wanted the default work status to be locked, and then for the finance administrator to explicitly open up the category & time period for users. We never got it to work in a really clean manner.
For the work status check to take effect, there must be records in the tblFinanceLock table (where Finance is the applcation name). And the only way that records normally get into that table is by changing the work status manually. We played around with a SQL script to populate that table, to automatically set the status to the first level (locked), but never found something that we were comfortable with.
I'd be curious to hear if someone's made something like that work well.