topic Re: Recommendations for Custom Self-Registration App. in Alfresco Archive

Recommendations for Custom Self-Registration App.

pjaromin — Tue, 16 Apr 2013 19:18:06 GMT

I've been charged with creating a basic self-registration app for Alfresco. The basic app would capture a user's registration information - which would essentially mirror syserson‍.The external app then needs to store this registration in the repository and kick off an approval workflow so that an

Re: Recommendations for Custom Self-Registration App.

pawel_rzeszowsk — Wed, 17 Apr 2013 06:16:12 GMT

You can enable a user account in your workflow using javascript or java.
In javascript the code would look something like this:
<javascript>
var query = "@usr\\:username:\"youserToFindName\"";
var userStoreReference = "user://alfrescoUserStore";
var usersResultList = search.luceneSearch(userStoreReference, query);
var userInTheUserStore = usersResultList[0];
userInTheUserStore.properties["usr:enabled"] = true;
userInTheUserStore.save();
</javascript>

Best Regards,
Pawel Rzeszowski.

Re: Recommendations for Custom Self-Registration App.

pjaromin — Wed, 17 Apr 2013 12:10:21 GMT

Thanks, Pawel. That should come in handy!

I've started the process and have verified that you can put a

sys:person‍

node in a workflow as the workflow item. So now I need to sort out the best way to modify the workflow task edit form so that the person item either displays all pertinent information, or the link goes to an appropriate view. Right now, if you click on a

sys:person‍

item in workflow in Share, the document-details page is not very happy.

Re: Recommendations for Custom Self-Registration App.

pawel_rzeszowsk — Wed, 17 Apr 2013 13:27:11 GMT

you can put just a username to your workflow as string, which will be used in Lucene query.
According to display cmerson in workflow form please take a look at authority.ftl and taskowner.ftl.
Regards,
Pawel Rzeszowski.

Re: Recommendations for Custom Self-Registration App.

pjaromin — Mon, 22 Apr 2013 22:11:56 GMT

I wound up putting the person in the workflow - it was easier and cleaner as I was able to create a customized packageItems component that showed a link to the user profile.

I tried initially using people.enableAccount, but for some reason 'runAs' in my Activiti workflow didn't work…and after a couple frustrating debugging sessions I decided to try your previously supplied query. This worked just fine on my local dev system (using maven), however when migrated to a server it complained that SOLR can't search the user store.

So, ultimately I wound up overridding enableAccount to wrap in a 'runAsSystem' call. In my environment only admins have access to the data dictionary or javascript console, so the risks should be minimal.

Hopefully I'll figure out why runAs isn't working - it appears to be a bug, though I don't have time to determine this. Obviously enabling a user within a workflow script is outside the typical use case and likely why this isn't working for me ootb.

Thanks!

-Patrick