It’s been a while since I put up a technical post so I thought I’d kick off with some Assignment Manager action! Since Siebel Bootcamp, I’ve not touched on Assignment Manager in any of my projects. My current Public Sector implementation is using it for Case assignment and it’s given me an opportunity to get to know the technology a bit better. Hopefully I can share some of that with you over the coming weeks.
For those not in the know, Assignment Manager (AM from now on, to save me typing!) is a technology that allows the allocation of objects such as Opportunities, Service Requests, Cases and Activities, to ownership objects within your Siebel implementation: employees, positions and organisations. It does this, is essence, using some key features:
- Assignment Objects
- Assignment Criteria
- Assignment Rules
- Assignment Skills
Think of objects as a parallel abstraction of the data layer to a business layer. Not quite a Business Component but sharing many of the same properties: imagine a simplified BC definition, where fields are exposed via columns and joins. These make up the SR, Opportunity objects and the key attributes of those which will be the basis of their assignment. Assignment criteria, rules and skills all go towards matching up attributes of the object to equivalent or related attributes of the assignee, be that a person, position, organisation or a mixture of both.
Don’t get too bogged down in the detail of it all though. In the coming weeks, I’ll hopefully show you that’s it’s not all that complicated and defining new Assignment Criteria and associated Assignment Rules is actually pretty straight forward!
If you can’t wait any longer, there’s always the Assignment Manager Guide on Bookshelf!
See you next time!
