<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Workflow visibility between users in Share in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/workflow-visibility-between-users-in-share/m-p/287291#M240421</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thank you for your reply.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;workflowIds cannot be guessed easily, however someone might try to discover them with a script, say.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;What I meant by "by design" was is it an acknowledged and accepted feature that the system is like this, i.e. userB can see details of userA's workflow if he can guess or find out the workflowId, even if he himself (i.e. userB) has nothing to do with the workflow.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 07 Jun 2013 07:58:26 GMT</pubDate>
    <dc:creator>dhd</dc:creator>
    <dc:date>2013-06-07T07:58:26Z</dc:date>
    <item>
      <title>Workflow visibility between users in Share</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/workflow-visibility-between-users-in-share/m-p/287289#M240419</link>
      <description>Hi,As far as I understand it, there is nothing to stop users seeing each other's workflows as created in Share.For example, if you have 2 Share users userA, userB (who are not members of any sites), userA can create an ad-hoc task (assigned to himself, say), details of which might be accessible at:&amp;nbsp;</description>
      <pubDate>Thu, 06 Jun 2013 16:18:45 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/workflow-visibility-between-users-in-share/m-p/287289#M240419</guid>
      <dc:creator>dhd</dc:creator>
      <dc:date>2013-06-06T16:18:45Z</dc:date>
    </item>
    <item>
      <title>Re: Workflow visibility between users in Share</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/workflow-visibility-between-users-in-share/m-p/287290#M240420</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;workflow id is randomly generated number so I do not think it can be guessed easily and to answer you question this is not "by design" thing. User whom task is assigned can only see the workflow details.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Jun 2013 17:03:04 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/workflow-visibility-between-users-in-share/m-p/287290#M240420</guid>
      <dc:creator>mitpatoliya</dc:creator>
      <dc:date>2013-06-06T17:03:04Z</dc:date>
    </item>
    <item>
      <title>Re: Workflow visibility between users in Share</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/workflow-visibility-between-users-in-share/m-p/287291#M240421</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thank you for your reply.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;workflowIds cannot be guessed easily, however someone might try to discover them with a script, say.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;What I meant by "by design" was is it an acknowledged and accepted feature that the system is like this, i.e. userB can see details of userA's workflow if he can guess or find out the workflowId, even if he himself (i.e. userB) has nothing to do with the workflow.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Jun 2013 07:58:26 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/workflow-visibility-between-users-in-share/m-p/287291#M240421</guid>
      <dc:creator>dhd</dc:creator>
      <dc:date>2013-06-07T07:58:26Z</dc:date>
    </item>
  </channel>
</rss>

