<?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 Immutable process instance variables in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/immutable-process-instance-variables/m-p/218129#M171259</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi, I was wondering if there were any suggestions for ways to implement immutable process instance variables using Activiti Engine and the Activiti REST API.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I am designing a process where process instance variables are set upon creation for an initial "approval request" and these variables must not be changed by downstream tasks. To my knowledge, process instance variables can be overridden at any point in time by the REST API. I have been thinking about the best ways to enforce immutability of these variables, but I wanted to see if there were other options, and perhaps guidance for option 2.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;1. Create custom endpoints for process instance creation, task approval, for this particular process definition. This would allow me to restrict or validate user input for downstream tasks.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2. Create a task listener that will check if an existing process variable has been changed, and "reject" the task from completing the task – though I am not sure how to implement this option. Can the listeners autowire beans?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any guidance is appreciated.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 29 Apr 2016 16:08:59 GMT</pubDate>
    <dc:creator>slickrobert</dc:creator>
    <dc:date>2016-04-29T16:08:59Z</dc:date>
    <item>
      <title>Immutable process instance variables</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/immutable-process-instance-variables/m-p/218129#M171259</link>
      <description>Hi, I was wondering if there were any suggestions for ways to implement immutable process instance variables using Activiti Engine and the Activiti REST API.I am designing a process where process instance variables are set upon creation for an initial "approval request" and these variables must not</description>
      <pubDate>Fri, 29 Apr 2016 16:08:59 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/immutable-process-instance-variables/m-p/218129#M171259</guid>
      <dc:creator>slickrobert</dc:creator>
      <dc:date>2016-04-29T16:08:59Z</dc:date>
    </item>
    <item>
      <title>Re: Immutable process instance variables</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/immutable-process-instance-variables/m-p/218130#M171260</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Option 2 is feasible. Use Event handlers and VARIABLE_UPDATED event (&lt;/SPAN&gt;&lt;A href="http://activiti.org/userguide/index.html#eventDispatcherEventTypes" rel="nofollow noopener noreferrer"&gt;http://activiti.org/userguide/index.html#eventDispatcherEventTypes&lt;/A&gt;&lt;SPAN&gt;).&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Listen to the event and throw an exception afterwards.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Martin&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 May 2016 04:49:51 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/immutable-process-instance-variables/m-p/218130#M171260</guid>
      <dc:creator>martin_grofcik</dc:creator>
      <dc:date>2016-05-02T04:49:51Z</dc:date>
    </item>
    <item>
      <title>Re: Immutable process instance variables</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/immutable-process-instance-variables/m-p/218131#M171261</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Option 1 is feasable too - the REST app is a regular Spring MVC app with component scanning. Put your custom endpoints in the right package and that's it.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 May 2016 12:38:33 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/immutable-process-instance-variables/m-p/218131#M171261</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2016-05-03T12:38:33Z</dc:date>
    </item>
  </channel>
</rss>

