Hi,
I have created a VCI along with its component though One Desktop and published it successfully.
Now, my teammates are unable to find the component, but they could find the VCI in both Desktop and Web and they are able to utilize the VCI as well.
Any information regarding this would be helpful. Thanks!
Note: Ataccama V15.4
Best answer by anna.spakova
Hi
all VCIs belong under some source so it is likely that in your case the VCI inherits the group permissions from this data source. If you open the share options in the VCI, you can see the groups with the lock symbol - if you place the mouse cursor on it, it will tell you how is the access inherited:
However, in case of components, there is no parent object that would give access to all components automatically. So the access is only given to the creator user who becomes the owner of it, and this user then needs to share the component manually with other users/groups that should have access to it as well. That can be done using the share button.
To automate this, I can think of only some orchestration process using a notification handler, which would require some effort to implement. In short, when a new component is created, a workflow on the orchestration server would be triggered that would share the component automatically. But components are usually quite technical, and only a handful of users usually require access to them. So it might not be worth the effort. But let me know if this is something interesting for you, and I can share links to more resources about this topic.
I hope it is clear now, but let me know if you need further information.
Kind regards,
Anna
+3Hi
Thank you!
Hi
But VCI is visible both on web and desktop to everyone in the team
.
+3Hi
can you confirm if the users donwloaded changes in the ONE Desktop tool (using refresh on the connection, disconnect/connect back to it)? If you say - they can see the VCI in ONE Desktop, can you send a screenshot of that? They see an old version or what do you mean by that? Can they right-click and run Download? That can also download updates on it.
Other than that, I can only think of permissions on the components → if you navigate in the UI to Components and track down the relevant Transformation (VCI) one, you can check who has access to it:
Let me know if any of this helps please.
Kind regards,
Anna
Hi
I have checked the access in UI, surprisingly VCI is created with full access to entire group whereas its component is created with individual user access to me alone.
Please let me know if anything can be done while publishing component to give access to entire group?
+3Hi
all VCIs belong under some source so it is likely that in your case the VCI inherits the group permissions from this data source. If you open the share options in the VCI, you can see the groups with the lock symbol - if you place the mouse cursor on it, it will tell you how is the access inherited:
However, in case of components, there is no parent object that would give access to all components automatically. So the access is only given to the creator user who becomes the owner of it, and this user then needs to share the component manually with other users/groups that should have access to it as well. That can be done using the share button.
To automate this, I can think of only some orchestration process using a notification handler, which would require some effort to implement. In short, when a new component is created, a workflow on the orchestration server would be triggered that would share the component automatically. But components are usually quite technical, and only a handful of users usually require access to them. So it might not be worth the effort. But let me know if this is something interesting for you, and I can share links to more resources about this topic.
I hope it is clear now, but let me know if you need further information.
Kind regards,
Anna
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
