comanage-dev - Re: [comanage-dev] Changing COs (CO-767 & CO-416)

Subject: COmanage Developers List

List archive

Re: [comanage-dev] Changing COs (CO-767 & CO-416)

From: Arlen Johnson <>
To:
Subject: Re: [comanage-dev] Changing COs (CO-767 & CO-416)
Date: Fri, 21 Feb 2014 12:24:52 -0500

On 2/19/2014 6:41 PM, Benn Oshrin wrote:

Currently, there is no "entry point" into a CO, only the CMP (/registry). I think we need to allow something like /registry/co:2 to be a valid entry point (CO specific dashboard?).

If users could select their "default" CO, it might make this simpler. If they are in only one CO, that's their default. If in multiple, they choose which will first appear when they log in. Perhaps "None - let me choose" is an option as well, which would end up presenting them with the global dashboard rather than the CO-specific dashboard.

In either case, what I present for menuing is based on the CO in use (current or default). (And if "none - let me choose", they must first select their CO to use the menus...this option might only be of value to a platform admin.)

On the other hand, you'd noted that you expect direct linking into the COs ...is that the common use case?

[comanage-dev] Platform menu (CO-416), Arlen Johnson, 02/17/2014
- [comanage-dev] Changing COs (CO-767 & CO-416), Arlen Johnson, 02/17/2014
  - Re: [comanage-dev] Changing COs (CO-767 & CO-416), Benn Oshrin, 02/19/2014
    - Re: [comanage-dev] Changing COs (CO-767 & CO-416), Arlen Johnson, 02/20/2014
      - Re: [comanage-dev] Changing COs (CO-767 & CO-416), Arlen Johnson, 02/21/2014
        
        Re: [comanage-dev] Changing COs (CO-767 & CO-416), Scott Koranda, 02/22/2014
- Re: [comanage-dev] Platform menu (CO-416), Benn Oshrin, 02/19/2014

List archive

Re: [comanage-dev] Changing COs (CO-767 & CO-416)