I am wondering if it is possible to add new properties to Tasks detail screen under Process Manager (Opportunity).  We would like to add two new fields.

I tried to create a new BO that inherits from TaskItem BO and add fields but then there is no way to tell iMIS to use the new BO. It seems like it is all hardcoded.

I also tried to add those fields to TaskItem table and edit TaskItem BO to add those fields although I know that would be overwritten by the upgrade but that did't work either.

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.

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.

This is a simple console application which moves all opportunites to a specific stage.