Implications of changing Inactive Tessitura Usernames? (Operators not Constituents)

Hello all,

Does anyone have a practice of modifying Tessitura operator usernames when the staff member is no longer with the organisation and has been made Inactive?

I am finding that many parts of the interface will still let you select an Inactive username when typing the first few letters, and if you hit one of the Inactives, you get an error which stops you continuing to type.

My first thought is to append an underscore at the start of the usernames to prevent this. Eg: Jane Smith's inactive username would change from jsmith to _jsmith.

Does anyone know of a reason to not go down this path, or have a better solution?

Best,

Nicholas 

Parents
  • I can’t think of a reason not to — it looks like some solicitor functions are actually foreign-keyed to that table, so you may see some audit logs reflect the _-prepended username. Most audit logs won’t change.

    I may have found a bug in Security just now where if you change the name of a user and then try to create one identical to the old name, you get a (security) application crash. So, that’s interesting, but at least then you won’t accidentally create a new user with the same username as an old one!

    I think the bigger problem here is that Tessitura’s UI has those kinds of bugs — in this case related to premature input validation. Am I the only person who gets absolutely infuriated by this sort of thing? I’ve been sitting on a 14KB text file full of all the UI annoyances I’ve found in four months of using the software, waiting for some free time to parse it all out and submit formal defect reports. Do all PowerBuilder apps have similar flaws, or is it just us?

    -Nick

    On Apr 28, 2014, at 8:13 PM, Nicholas Hudson-Ellis <bounce-nicholashudsonellis2615@tessituranetwork.com> wrote:

    Hello all,

    Does anyone have a practice of modifying Tessitura operator usernames when the staff member is no longer with the organisation and has been made Inactive?

    I am finding that many parts of the interface will still let you select an Inactive username when typing the first few letters, and if you hit one of the Inactives, you get an error which stops you continuing to type.

    My first thought is to append an underscore at the start of the usernames to prevent this. Eg: Jane Smith's inactive username would change from jsmith to _jsmith.

    Does anyone know of a reason to not go down this path, or have a better solution?

    Best,

    Nicholas 




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

  • Unknown said:
    I think the bigger problem here is that Tessitura’s UI has those kinds of bugs — in this case related to premature input validation. Am I the only person who gets absolutely infuriated by this sort of thing? [...] Do all PowerBuilder apps have similar flaws, or is it just us?

    Do you refer to the "an unexpected error has occurred" followed by a client crash kind of thing? If yes, no, you are not alone.

Reply
  • Unknown said:
    I think the bigger problem here is that Tessitura’s UI has those kinds of bugs — in this case related to premature input validation. Am I the only person who gets absolutely infuriated by this sort of thing? [...] Do all PowerBuilder apps have similar flaws, or is it just us?

    Do you refer to the "an unexpected error has occurred" followed by a client crash kind of thing? If yes, no, you are not alone.

Children
No Data