Service Market 6.0.8


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:

  1. 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).
  2. Create a new Product Question with the type User.
  3. Create a JSONAttributes Generator with one input called “objectId”, and “thumbnailPhoto” in the Valid Attributes box.
  4. Create a Request Service Product, set it as active and add the two product questions from steps 1 and 2.
  5. 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:CaptureUserImageConf
  6. Open Workflow Manager, and open the WM_Request_Service workflow
  7. 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.
  8. Add a SortQuestions activity from the AteaSpintop.Activities.Question namespace, and map the Order parameter to the Order property of the Workflow.
  9. 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 WorkflowCapturePROPs
  10. Save, and compile the workflow after incrementing the version number.
  11. 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.CaptureServiceImage

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!

Posted in Uncategorized | Leave a comment

Service Market 6.0.7

It’s time for a new release of Service Market! This time it’s 6.0.7. We continue our quest for the ultimate automated self service portal, and we’ve added a few more features to help us along the way:

OS/platform filter for Software – Software can now be filtered on Tags and depending on the target computer certain tags will be pre-selected. The filter is set by default on a best effort basis using the SCCM and the user is able to “opt out” by clearing the filter.


If we get a bit technical, we could have a look at a new table in the database: ProductTagsOsMapping. This table is used to map from the rather technical names for OS’s that SCCM uses internally (and which we sniff out from there) to a more user friendly tag name which can be used to tag up your software. We have pre-populated this table with most Windows versions, but feel free to add more default OS’s, e.g. MacOS. Feel free to contact us with suggestions and questions regarding this!

Offerings can now connect to an ad group or OU – We’ve had a secret AD group functionality regarding Offerings for a while, but now we’ve made it official. Through the Offerings administration service you can now connect an offering to AD groups and or OUs. Users will automatically get access to offerings based on these if they are configured. For example, this makes it easy to have a Product offering for each country, if the users are placed in country OU’s for example. This is also a part of our ongoing mission to make our Department logic optional, and make it possible to base this kind of business logic purely on AD (or other systems’) information.


Request Product Beta Toolkit – In this version we’re also taking steps towards making a more flexible service concept happen. Let’s call it Request Product, a configurable generic complementing our standard services. Making use of recent feature updates like custom workflows, powershell scripts and generators, it’s now possible to set up a Service product to perform a lot of stuff. To help with this there’s a new Image Product Question, a new Password type for text boxes, and a few generators that will populate Product Questions depending on attributes. All of them take an identifier and a list of attributes to fetch as input, and will (should if you write your own Powershell) return the attributes as properties in a stringified JSON object. There’s also new or updated Workflow activities to help performing the services.


You can also set up the Service table to get (some) products directly in the menu, by adding a new row. The magic happens in the new QueryString column, where you can tell the RequestGenericService usercontrol which product to go to. (For the curious it’s the “p” or “d” parameter which should be set to the productID, try it out for yourselves to see the difference).


Examples of where this might come in handy could be customized services where you can set AD attributes (like Thumbnail Image) arbitrarily, or automate through external systems with Question forms running Powershell in the back-end. Nearly everything (of course) is possible! :) We’re happy to assist you with trying this out, contact us with a use case in mind and we’ll se what we can do. Note that these features have yet to make into the documentation, but any questions will be answered as soon as possible!

Happy installing and upgrading!

Posted in Press Release, Releases, Service Market | Leave a comment

Service Market 6.0.6

Service Market + PowerShell = This version!

We’re extending a hand to all you scripting people out there. With version 6.0.6 comes the possibility to add your completely own PowerShell scripts to be run in the Service Market standard workflows for virtually any product. The scripting functionality is primarily intended for Services utilizing Product Questions (i.e. Request Hardware/Software/Service/Incident Report and Deployment services) but will work in all workflows (with fixed value inputs).

The scripts themselves reside in a configurable location and can be searched and added to products in the new Scripts section of Product Administration


For each parameter (and an output) you can assign the product’s Questions independently or enter a fixed value. If enabled and properly configured to a Question, the output gets written back to the Order database in the workflow, and if applicable, to the Vendor or Completion mail before they are sent, so you can se the results in the My Requests service or mailbox.

Also, there is now a standard Generator that runs Powershell! By configuring it to run a PS (with one argument only) anywhere on the disk. The parameter sent to the script you can setup with inputs through the use of the standard Pattern Generator, so for example if you need two Question inputs, you can use this to concatenate them with a suitable separator before running the script.

As a finishing touch we’ve addressed an issue that new versions of Service Market needed some users to empty their cache to see new functionality. Hopefully this should no longer occur.

Please let us know if you come up with nifty ideas and solutions, especially with the new PowerShell possibilities – Happy scripting!

Posted in Releases, Service Market | Leave a comment
Page 1 of 3112345...102030...Last »
  • Categories

  • Archives

  • Recent Posts