Hi

I' looking for specific information on the management of roles in process manager. As an example there is a role called 'Regional Manager' however i can't see how it was created, or where it can edited or deleted. Any ideas?

Thanks

Jay

Hi

I've created a new class for use in process manager. I'm looking for a way however to get some contact information, specifically the Paid Thru date, onto the sumary tab of a project. Has anyone had any success with this or similar?

Thanks

Jay

I have created a branch of the Opportunity class in iMIS 15.0.3 to manage a specific process for a customer. One of the properties for this class is called 'Product' is displayed as a drop down list, which has been configured in the business object designer.

When I create a new project, it shows me the drop down list correctly and also stores the 'value' in the database as designed. The problem is that when I look at the summary tab, it shows the value from the database for that field, not the description.

Question: In process manager I want to be able to modify the Sales Opportunity Quality lookup field to allow for more than the basic three quality grades. We have numerous grades for our products which can change quite often. I know I can modify the OpportunitySales object and property for Quality by adjusting the Value List under the Values tab in Business Object Designer. However I do not want to give my general staff who will need to make frequent adjustment to this list access to the Business Object Designer. Is there a way to do this?

I tried searching for a quick guide on how to do this and couldn't find anything, although I hear there are details on the documentation site. Anyway, while I think of it, here is a very quick "how to" on setting up a new process type, with a new process class.

1. Create a new SQL table - simple way is to duplicate the create table schema for OpportunityMainMember and make the necessary changes to the column names and constraints. Re-order the columns if required as this is the order they will appear on the screen. Remember to have an OpportunityKey.

The iMIS Reference for Process Manager even states specifically that: "Default Opportunity Classes (Donor, Member, Sales) are provided in iMIS. You can buil additional Opportunity Classes that meet the unique needs for your organization."

Unfortunately, the description, details, explaination stops there. There is nothing documented anywhere else about creating additional Opportunity Classes. I can only hope that as the iSA rolls out with more features that there is additional documentation and functionality built into it for the end-users to create and manage, not just ASI development.

Hi,

Has anyone developed a method for creating opportunities either through the API or through a stored procedure based on another action in iMIS? For example, I need an opportunity automatically created when someone registers for an event.

Thanks,

Troy

I am trying to write actions that record all changes made to an opportunity. The requirements include tracking changes to contact, owners, competitors, tasks, etc.

I have created actions that will successfully record the changes. The problem I am running into is that for fields larger than 250 characters the data gets truncated. My data gets written to a custom table to a column is large enough to accommodate the data.

I have a request from a client to either modify the existing task list, or develop an additional one to accomodate the following functionality.

Tickboxes should be added to the task list so that tasks can be changed en masse as illustrated in the screen attached

I am working on a Process Manager object action to update owners of opportunities. Essentially we need to remove the default owners assigned through relationships for certain opportunity types. E.G. A customer sale uses the default owners defined by relationships (a Regional Sales Manager and a Customer Care Representative) however, consulting does not – a consultant who creates a new consulting service sale will not be followed up on by a Customer Care Rep – it will go through ASI’s PMO Office. So we want to remove the Customer Care default role and rely upon the default owner assigned by the opportunity type instead.