• Creator
  • #3490

    Hello !
    I find the way the association is working, not very clear.
    Generaly, in NDS, administrators can see association in 2 ways. Lets take groups as an exemple.
    If UserA.Acme is member of Group_GWFormativ.Acme, I will see him in “Memberlist” of .Group_GWFormativ.Acme and I will see Group_GWFormativ.Acme in “Group membership” of UserA.Acme, making it clear and easy to manipulate group assignment.
    With the Formativ association process, we just get a reply saying “association was made”, and we could see from the client side what configuration we are linked to, but I can’t review this association from NWAdmin.
    Currently we are etsting, and some users are associated via OU, groups, or their relative user object.
    Unless we start the client, it makes it very difficult to see what is the current valid association.
    I should be able to do 2 things:
    1/ See who/what is currently associated to a configuration.
    2/ See what configuration is associated to an object (requires a new TAB under this object).

  • Author
  • #5227
    Support 2

    Thank you for your feedback, which I will pass onto our engineering team for review. You can see if an User/Group/OU/O object is associated with a Formativ Configuration Object by viewing its See Also property, which is where the FDN of the Configuration object is stored when the Associate button is used.

    Your feedback will contribute to the development of future enhancements in this area.


    Advansys Support


    Interesting aspect!

    We are also missing this feature to see these associations from both ways (from user/OU/group to Formativ Config-Objects AND(!) back) We are using Formativ Wouldn´t it be nice to create referencing attributes for this in the objectclasses of user, group and organizational units?

    Thanks for your patience!
    Gerrit 🙂

    Support 1a

    This feature has a high priority in our enhancement database, and will most likely be made available some time after Brainshare SLC.


    Advansys Support


    I’ve just started to install my purchased copy of your product and so have just started to look at the NDS intergration. First off, thanks for providing some as many venders do not bother, but the use of See Also is a strange solution as it does not follow any standard methods.

    I can see why your developers used this solution and the fixed named ‘Org Role’ object as they remove the need for the Formativ software having its own controlling ‘root’ object in the tree, instead things are infered from the user object.

    It maybe better for Formativ to have its own master object that is linked to the GW domain/Post office objects so that it can be found by checking which post office a user is defined in. Once you have found the Formativ object you can then use it to discover who have admin rights etc, without needing the Org role object.

    It would also be nice to see the Configuration Object being removed and a user being allowed access to many applet containers directly. At the moment the Configuration Object just seem to be a weak access control point that can be replaced with standard access rights checking – once Formativ had its own control object that lists all the
    Applet collections available to it.

    As I noted before what you have supplied is still better than most venders so thanks.


    Support 1a


    Thank you very much for taking the time to provide your detailed suggestions. We always welcome feedback and suggestions from our user base, and your suggestions are warmly accepted.

    I’ve added your ideas to our enhancement database. We draw upon this information whenever a maintenance release or new version is planned, so it will be seriously considered at the appropriate time.

    Once again, thank you for taking the time to share your ideas.

    Kind rehards,

    Advansys Support

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.