Limit the "Add New" to a single top level in a levelled application?
Does anyone know of a hack to stop users from adding a New Record at a level below the parent top level of the application?
- Community Thread
- Forum Thread
- RSA Archer
- RSA Archer Suite
We introduced an unsavable scenario via DDEs. Basically, if a L2/L3/etc doesn't have an associated L1, we require a field they don't have access to such that they cannot save the record. We also display a Text Box on the top of the record stating this fact so they know they can't save.
Not ideal, but gets the job done.
Yeah that's exactly what I've implemented. Unfortunately our test user still got confused, rather than turning back & adding a parent record as stated, they give up! For all the configurable things in Archer... it's strange that this isn't...yet!