Variables not being resolved in Workspace

Hi,

This feature hasn't been implemented in Workspace nor Password Hub yet. However, we have a task for this on our internal roadmap.

Best regards,

Thanks Sébastien, any ETA on when this feature will be available? Its absense makes Workspace somewhat unusable for Data sources that use variables extensively.

Hi,

I understand how important this feature is to you. Given that its development involves coordination with other products, each having their own timelines and updates, providing an exact ETA can be challenging. Rest assured, I'm on top of this and will ensure to keep you informed with any progress or updates as they happen. Your patience and understanding are greatly appreciated.

Best regards,

ok, thanks Sébastien, I certainly understand you guys have lots going on :)

Hello Sébastien,

Any update on this one?

Thanks
Joe

Hi, the support for the variables is currently available in Workspace with Hub Business. To create and refer to the variable, don’t forget that you have to use RDM.

Best regards,

Hello Sébastien,

Still seeing $PARENT_NAME$ not resolving in Workspace, (nor Hub Biz Web UI). Comparatively, DVLS web UI resolves them correctly.

As I mentioned previously, the absense of variable resolution in either Workspace or Hub UI makes those products unusable for larger commercial deployments where variables tend to be used regularly. With the capability of Web Connect client in Hub, customers sometimes want to use this without requiring full RDM licence for segments of users.

Thanks
Joe

Hi, as it stands, we support these variables:

1. $HOST$
2. $DOMAIN$
3. $PORT$
4. $HOST_WITH_PORT$
5. $PARENT_HOST$
6. $ALTERNATE_HOST$
7. $HOST_WITHOUT_DOMAIN$
8. $REPOSITORY_NAME$
9. $CREDENTIAL_EMAIL$
10. $CREDENTIAL_UPN$
11. $CONTACT_USERNAME$
12. $CONTACT_DOMAIN$
13. $VPN_USERNAME$
14. $VPN_DOMAIN$
15. $CUSTOM_FIELD1$ to $CUSTOM_FIELD5$

We can add other variables to this list. Besides PARENT_NAME, which variable would you want to be added to the list above?

Best regards,

Hello Sébastien,

Thanks, support for both $NAME$ and $PARENT_NAME$ would be great. Often I configure host type entries where the hostname attribute is set to $NAME$.domain.local, and sub connection entries are named $PARENT_NAME$ with host set to $PARENT_HOST$. This makes duplicating a host entry with sub connections efficient, because only the name attribute of the duplicated host needs to be updated.

Please let me know if you would like any additional info.

Thanks
Joe

Hello Joe,

That sounds great. I have already created a task in Workspace to include a few additional variables. I will inform you as soon as this is deployed to production.

Thank you.

Hi, just letting you know that the support of the variables $PARENT_NAME$ and $NAME$ will be added in the next Workspace version (2024.3.2) which should be out this week.

Best regards,

perfect, thanks Sébastien for the quick turnaround on this one.