K-Rise Systems

For a newly created app, the user session variables show lots of info that just come with from the EPUsers table, but these are not seen in the IDE anywhere. If the developer adds some to the User Properties, they will also show here, but to start, this could use some trimming of columns.

Here is a user created for a new app. no application properties/user property values Bug: the link has "Application Properties" and when opened, the widget has User Property Values

Key:
Move To Application Properties - seems like a good idea, but the developer should add this themselves. Or it should be auto added as an application property and seen when opened from the usermanagement page in the IDE
Valid - This is in the SaveUser widget from UserManagement page in IDE. This makes sense to be here.
Should Add - Should be added as a Label to SaveUser widget. Then it is Valid
Remnant from 4.8 - Should be removed. It is questionable whether this should stay in 5.1. Need feedback from internal team whether its being used.
System Only - Sounds like its useful for the system, but should not be in the application/user properties. We could consider hiding them, but run into issues in case the developer wants to make an application property of the same name. The System Only properties should go somewhere that is still able to be queried from a method if you need, but you have to know where to look for it.

• AddressNumber - Move To Application Properties
• CellPhoneNumber - Move To Application Properties
• CellProvider - Move To Application Properties
• Culture - Valid
• CurrentLoginTime - Should Add (only need one: CurrentLoginTime/LastLoginTime?)
• CurrentUserSessionId - System Only
• DateDeactivated - Remnant from 4.8
• DeactivationReason - Remnant from 4.8
• DefaultLanguage - Should Add
• Email - Valid
• FirstName - Valid
• ForcePasswordChange - Remnant from 4.8
• Icon - System Only
• IdentityProvider - Valid
• LabId - System Only
• LandingPage - Remnant from 4.8
• LastLoginTime - Should Add (only need one: CurrentLoginTime/LastLoginTime?)
• LastName - Valid
• LastPasswordChanged - Should Add
• LongDatePattern - Valid (Display Date Time Format?)
• OverrideAuthorization - Remnant from 4.8?
• ResetPasswordFlag - Remnant from 4.8
• SecurityAnswer - Remnant from 4.8
• SecurityAnswer2 - Remnant from 4.8
• SecurityAnswer3 - Remnant from 4.8
• SecurityAnswer4 - Remnant from 4.8
• SecurityAnswer5 - Remnant from 4.8
• SecurityLevel - Remnant from 4.8
• SecurityQuestion - Remnant from 4.8
• SecurityQuestion2 - Remnant from 4.8
• SecurityQuestion3 - Remnant from 4.8
• SecurityQuestion4 - Remnant from 4.8
• SecurityQuestion5 - Remnant from 4.8
• SetupComplete - System Only
• ShortDatePattern - Valid (Display Date Format?)
• TenantId - System Only
• TermsAccepted - Remnant from 4.8
• TimeZone - Valid
• Token - System Only
• UnsuccessfulAttemptCount - Should Add
• UserAuthorizationType - Should Add
• UserId - Valid
• UserPassword - System Only
• UserStatus - Should Add

Discussed this on a call today,

The list currently displays:

• EPUsers table columns
• application/user properties

These are in 3 areas:

1. The Edit User Link in user management page in IDE
2. The Application properties link in the user management page in IDE
3. Hidden system properties that cannot be edited in the IDE

Of these 3, only 1 and 2 make sense to show in the user tab in the logic canvas

So from this discussion, there are a few questions

Do we need a service to change user properties? Right now we have ModifyUserSession service for this, I think. would you ever need to change the user session variable of culture for example? Impersonation is not included in this, that is a special case for userauthorization.

should a new service allow you to permanently change a property?
Yes, we need to update language, culture, date format, name for a user in EASYCommerce

I reread this and had some new thoughts:

For application specific user properties, since they are specific to the application, EASYProcess cant determine whether they should be able to be changed or not. So it should give that ability.

Consider one EC tenant where a property is the "Region". It could be selected by the user when the login to know which country they are working in. It should be saved in the db because we could have a feature that the last selection made should be saved so the next time they login, it is auto selected.

So we need both services to change them in user session (we have this) and in the db.