Atea Global Services is pleased to announce the release of My Work in Atea Vergo.
My Work provides an overview for the current and upcoming work that needs to be accomplished by the logged in user.
A panel will show in My Work given that all of the following requirements are fulfilled:
- The plan has the logged in user as a team member
- The plan is dispatched
- Current Work:
- The plan’s start date is today’s date or earlier
- The plan’s end date is today’s date or later
- Upcoming Work:
- The plan’s start date is later than today’s date
My Work is available now.
If you cannot see the ‘Work’ item on the menu, please refresh your browser using Ctrl + F5.
It has come to our attention that a “bug”, or at least a weird feature, of .NET affects our recent releases (6.0.7/8 that we’re aware of). This causes users having an AD user object referencing an invalid SID to not be able to use most request services. Instead the message “An error occurred while enumerating the groups. The group could not be found.” will show in some way. This is not very common, but in domains where users have been migrated, we’ve seen this effect from having the sIDHistory attribute set.
So, if you have users experiencing this, and suspect this might be the case in your environment, we recommend you to replace the Accelerator.Infrastructure.dll in the \inetpub\wwwroot\[ServiceMarket]\bin to the hotfix one corresponding to your Service Market version. You can find it attached to this post, or download it from the usual FTP sites. Please contact us through email@example.com if you have any trouble!
The next version (in the near future) will also have the workaround that fixes this issue.
We’re sorry for any inconveniences caused!
Here are the links: Accelerator.Infrastructure.6.0.8 Accelerator.Infrastructure.6.0.7
It’s also time for a new release – Service Market 6.0.8! We’ve concentrated mainly on fixing stuff in this release, and so a lot of issues (some new and some old) have been resolved. Hopefully even some that you’ve been waiting for! This means not much new functionality will come out of the box, but behind the scenes a lot of the functionality is more stable.
We’ve also continued to explore integration with Office 365, and have some working example solutions built with our Product Question and Powershell building blocks. Please make an inquiry if you’re interested in what can be done.
Since there’s not much else to say about this release we’ll take a look at a typical Product as a service concept, that’s available, if you go through a few hoops. Please have a go if it suits your environment and let us know if it’s something you think should be in a coming standard release:
Setting a user’s AD Thumbnail Image through self service
This is now possible by utilizing the new Image question, the new JSONAttributes generator and some tweaking of the Request Service workflow. This is a brief description of how it can be done:
- Create a new Product Question with the type Image. It should have the ActiveDirectory area and “thumbnailPhoto” attribute (if that’s what you want to set).
- Create a new Product Question with the type User.
- Create a JSONAttributes Generator with one input called “objectId”, and “thumbnailPhoto” in the Valid Attributes box.
- Create a Request Service Product, set it as active and add the two product questions from steps 1 and 2.
- The user question should have the Generator from step 3 selected with itself mapped to the input, and Get from logged-in (or target, if that suits you better) user checked.All in all, this is what steps 1-5 should look like in Product Administration:
- Open Workflow Manager, and open the WM_Request_Service workflow
- Add a GetIdentityForUser activity from the AteaSpintop.Activities.AD namespace, preferably after the SendServiceVendorMail activity, and map the UserId property to the Order.RequestingEmployeeId property, and ADServerName to the ADServerName property of the Workflow.
- Add a SortQuestions activity from the AteaSpintop.Activities.Question namespace, and map the Order parameter to the Order property of the Workflow.
- Add a SetADAttributesFromQuestions activity from the AteaSpintop.Activities.Question namespace, and map
ObjectSID to the SID output property of the GetIdentityForUser activity in step 7
QuestionAnswer to the QuestionAnswer output of SortQuestions in step 8
DefaultDomainController to the ADServerName property of the Workflow
- Save, and compile the workflow after incrementing the version number.
- You are now good to go! Navigate to Request Service and add your product to the cart. Try changing the image and submit the order.
Amazing, isn’t it? In a production environment, you would probably want your own dedicated Service and maybe workflow to do this. This is also perfectly possible, and will be covered in detail in a later post
Happy installing and upgrading, and don’t forget telling us how this little experiment went!