Franceso: Thank you so much for this information! It was the guide I was looking for.
And, I think I broke it. I was using the demo site, admin and bellini. - (admin) Created a new flow using the assignPrinterRequest you referenced - (user) Created a request using the +, but did not fill in the form - (admin) claimed the unfilled request - (user) tried to fill out the form, could only delete it at that point - (admin) saw I could fill the form, but cancelled - (admin) unclaimed request And I got this: https://pastebin.com/CzmJNK7M Also, 1 question and 1 comment Q1: I've noticed this behaviour in the past, and it still seems to happen, both on my local and demo. When I'm logged in as the admin account, it will randomly log me out. I'm not inactive for any amount of time, haven't been logged in for very long, and.. boom. Different browsers, different machines, different times, different installs. It happens when I'm logged in as only the admin, or when logged in as both user and admin. I do recall a few random logouts on the user app, too. - Is this a known issue? C1: On the enduser app, the links for compressed and darkmode are strangely obscured. I wasn't sure what they were until I clicked on them. And, the changes I made on the enduser app spilled over to the console app. See attached image. Thank you again for your endless help and patience :) On Fri, Apr 26, 2019 at 4:49 AM Francesco Chicchiriccò <[email protected]> wrote: > Hi, > generally speaking, Flowable is not used "as-is" with all its features, > but embedded through an extension. > > In particular, Flowable Forms are not used as standalone entities, but > rather as they used to work since the time of Activiti, e.g. embedded in > the BPMN process definition. > Also the Flowable Modeler is embedded with only the capabilities > relevant to Syncope. > > If you want to see a working sample of user request (with forms), create > new user requests from Admin Console, name it "assignPrinterRequest" and > paste the content of > > > https://github.com/apache/syncope/blob/2_1_X/fit/core-reference/src/main/resources/assignPrinterRequest.bpmn20.xml > > or create another, name it "directorGroupRequest" and paste the content of > > > https://github.com/apache/syncope/blob/2_1_X/fit/core-reference/src/main/resources/directorGroupRequest.bpmn20.xml > > Once defined, user requests can be managed either via REST or Admin > Console (for approval) / Enduser UI (for starting / canceling / checking > status / etc.) > > Hope this clarifies. > Regards. > > On 25/04/19 06:58, Adam Levine wrote: > > On my maven build, and on the publicly hosted demo, I am unable to do > > anything with forms inside the flowable modeler. > > > > (extensions -> flowable -> select item from table -> flowable modeler) > > > > - When selecting an event, like the start event, and clicking on > > "form reference", an error is displayed: > > There was an error loading the forms. Try again later > > Also, the only enabled button is "Cancel". > > > > I ran the Flowable all-in-one to try and find a configuration > > difference. In this app, all the buttons are enabled, and no error > > message is shown. And, there is an entire menu bar up top (Processes, > > Case Models, Forms, Decision Tables, Apps) that is displayed. That > > menu bar is present on my syncope install when I open up the developer > > tools, but it's just not visible. > > > > Is this a matter of configuration? Does Flowable need to be running > > in parallel with syncope for form design? > > > > Thank you for any guidance you can provide. > > -- > Francesco Chicchiriccò > > Tirasa - Open Source Excellence > http://www.tirasa.net/ > > Member at The Apache Software Foundation > Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail > http://home.apache.org/~ilgrosso/ > >
