• State Suggested Answer
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 95 subscribers
  • Views 650 views
  • Users 0 members are here
Options
Related

Cloud user accounts (CSMUser) + Templates adjustments - best practices?

alexeyf
over 2 years ago

Hello all,

database tables for cloud target systems are used to store information about different target systems having different requirements to them etc. For example CSMUser is one of them.

I would like to adjust column templates for some attributes for one of the target systems we have (there may be several instances of this target system type) and the adjustments are only for this target system (type), so I would like to restrict the new templates.

And before hardcoding anything I would love to get to know if there is any best practice for this, specifically in case of CSM* tables as they are out-of-the-box meant to be one for everything tables.

Best Regards and thanks in advance,

Alexey

  • 0 over 2 years ago

    Hey Alexey,

    Well CSMUser is no different to any other namespace .... ADSAccount, LDAPAccount etc. All can support multiple domains/roots and all may need different behaviour depending on that.  So you just need to code something that distinguishes the target.  That might be referencing the value of UID_TSBAccountDef or it might be Ident_Domain or Ident_CSMRoot.  And of course in the case of account definition you want to react off the manage level.  So in short, there is no best practice really .... it's whatever works for you and makes your code readable and easy to understand.

    HTH, B,