nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

roles.xml and tsusers.xml

shahzamaj

TS71, WIn Server 2010
----------------------------
1) If I have added a user in TS71 using UI, do I still need to configure this user in tsusers.xml ? If not, then whats the need of this file ? Is it an alternate way of configuring TS users through file system ?
Or is it must to configure a user in tsusers.xml and his role in roles.xml ?

2) If thats the case, in what other files does a TS user need to be configured ?

3) I have another issue with a workflow. I have assigned a user a role of editor, reviewer, author and workflow is configured to be accessed by these roles. When this user initiates a job using this wf, he gets the message, "John Smith is not permitted to initiate the job". Now every other user gets the same message, even if they try to access this workflow with their own ID. Say Bill Laurier is trying to instantiate a job using this wf, he gets the message "John Smith is not permitted to initiate the job".
Now when I change the role of John Smith to master, then all users can instantiate this workflow. What can this be due to ?

Find more posts tagged with

Comments

Adam Stoller

TS71, WIn Server 2010
----------------------------
1) If I have added a user in TS71 using UI, do I still need to configure this user in tsusers.xml ? If not, then whats the need of this file ? Is it an alternate way of configuring TS users through file system ?
Or is it must to configure a user in tsusers.xml and his role in roles.xml ?

2) If thats the case, in what other files does a TS user need to be configured ?

tsusers.xml is the data-file used to record the TeamSite user entries - you can configure users directly via that file - but it is generally recommended that you use the GUI instead.

The roles.xml file is used for defining custom roles - not for associating users to roles.

TS uses a number of files for managing a number of things. If you are using TS Groups - then you could associate users with groups in the tsgroups.xml file - but again, it's generally recommended that you go through the GUI instead.

3) I have another issue with a workflow. I have assigned a user a role of editor, reviewer, author and workflow is configured to be accessed by these roles. When this user initiates a job using this wf, he gets the message, "John Smith is not permitted to initiate the job". Now every other user gets the same message, even if they try to access this workflow with their own ID. Say Bill Laurier is trying to instantiate a job using this wf, he gets the message "John Smith is not permitted to initiate the job".
Now when I change the role of John Smith to master, then all users can instantiate this workflow. What can this be due to ?

Is this a WFT or a WFM?
Is there a user hard-coded as the owner of the workflow?

shahzamaj

This is WFT.

owner name is not hardcoded. Following is the first line of workflow.

[html]
description="__TAG__('iw_submit_comment');">[/html]

Is this some kind of TS bug ? This is happening through UI. Currently, its happening on development, but it can happen on production also.

Any ideas to solve this issue please ?

Adam Stoller

3) I have another issue with a workflow. I have assigned a user a role of editor, reviewer, author and workflow is configured to be accessed by these roles. When this user initiates a job using this wf, he gets the message, "John Smith is not permitted to initiate the job". Now every other user gets the same message, even if they try to access this workflow with their own ID. Say Bill Laurier is trying to instantiate a job using this wf, he gets the message "John Smith is not permitted to initiate the job".
Now when I change the role of John Smith to master, then all users can instantiate this workflow. What can this be due to ?

Is this a WFT or a WFM?
Is there a user hard-coded as the owner of the workflow?

This is WFT.
owner name is not hardcoded. Following is the first line of workflow.
[html]
description="__TAG__('iw_submit_comment');">[/html]

Is this some kind of TS bug ? This is happening through UI. Currently, its happening on development, but it can happen on production also.

Any ideas to solve this issue please ?

I wonder about the exactness of the error message - My first guess would be that the WFT contains a submittask owned also by iw_user - and that if the job owner is only reviewer and/or author in the particular branch - that the workflow engine is detecting that the submittask will fail and displaying that error message.

However, that explanation does not completely fit the information that you have supplied - so while you say that the job owner is not hard-coded - is the name "John Smith" hard-coded at the owner of any tasks in the WFT? Or hard-coded as a shared-by member of any grouptask in the WFT? Or, if not hard-coded, an actual member of a group used for a grouptask in the WFT?

Having developed and debugged TeamSite workflows for over 10 years, I cannot help thinking that you are not providing all the facts, accurately, and that there is some aspect of the issue that you have omitted which is actually the source of the problem, but we won't be able to figure that out since we are not in a position to do so.