Interface UserSubStates


public interface UserSubStates
This interface contains some commonly used sub states for platform users as a more specialized state information. Beside those predefined sub states, you can create your custom ones as you like, only the states are fixed by the platform, the sub states can be chosen freely.
Author:
Micha Kiener
  • Field Summary

    Fields
    Modifier and Type
    Field
    Description
    static final String
    Use this one as the default in combination with the active state of a user.
    static final String
    You can use this sub state while the user is in deactivation process (e.g.
    static final String
    Use this one as the default in combination with the inactive state of a user.
    static final String
    You can use this sub state while the user is initializing (e.g.
    static final String
    You can use this sub state while the user is in reactivation process (e.g.
  • Field Details

    • ACTIVE

      static final String ACTIVE
      Use this one as the default in combination with the active state of a user.
      See Also:
    • INACTIVE

      static final String INACTIVE
      Use this one as the default in combination with the inactive state of a user.
      See Also:
    • INITIALIZING

      static final String INITIALIZING
      You can use this sub state while the user is initializing (e.g. if it takes a long time when creating and initializing a user, most likely happening within several transactions and not just one). This might be the case if an initializing process is triggered upon creation of a user.
      See Also:
    • DEACTIVATING

      static final String DEACTIVATING
      You can use this sub state while the user is in deactivation process (e.g. if it takes a long time when deactivating a user, most likely happening within several transactions and not just one). This might be the case if a deactivation process is triggered upon deactivation of a user.
      See Also:
    • REACTIVATING

      static final String REACTIVATING
      You can use this sub state while the user is in reactivation process (e.g. if it takes a long time when reactivating a user, most likely happening within several transactions and not just one). This might be the case if a reactivation process is triggered upon reactivation of a user.
      See Also: