This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for Spotfire products and services. It is for informational purposes only and its contents are subject to change without notice. Planning to implement - generally 6-12 months out. Likely to Implement - generally means 12-18 months out.
Copyright © 2014-2023 Cloud Software Group, Inc. All Rights Reserved.
Cloud Software Group, Inc. ("Company") follows the EU Standard Contractual Clauses as per the Company's Data Processing Agreement.
Terms of Use |
Privacy Policy |
Trademarks |
Patents |
Contact Us
Hi Norbert,
Thank you for your note.
I know about it. But this is not a case in our situation. We use existing AD groups a nd there are no name convention.
Before version 4 we were able to sort list in Administrative Console. It allowed to check if this AD group wasn't added already.
I'm not sure if you are aware that starting from Spotfire Server v6.0 it was possible to use wildcard characters for matching AD group names. This for us has completely eliminated the need to change the config file for adding a new AD group as we use a specific group naming convention, so all new AD groups are automatically picked up by the server as soon as they are created and synced. See release notes for 6.0: https://docs.tibco.com/pub/spotfire_server/6.0.0-november-2013/TIB_sfire_server_doc_6.0.0_relnotes.pdf (page 4, other enhancements)