Sage CRM Introducing a custom table to a workflow

Hi,

I have tried the route of making workfow buttons conditionally visible and I think that is the best solution. But how can I tell the opportunity workflow that the check field in the Residence custom table is Null and therefore the button should be hidden. ( I only want the next button to show if that check field in the Residence table is null)

I can't quite think how I pass that info across!

Thanks

You need to have a field on the opportunity that contains a check value. A date field or something like that. Then you hide the butons on the oppo workflow when this field contains nothing. This means the next workflow buttons do not show until there is a value in that field. In your Residence entity you will need an update tablescript that updates the value in the opportunity with a date when it is updated with the required values. This can be done via a separate workflow on the custom entity or just as simple tablescript. So what happens is that you will need to train the users that when they get to that point in the opportunity workflow, things cannot progress until they update the Residence entity with the required data. When they do that, the tablescript or workflow adds a date into the hidden field on the opportunity which will then allow the next steps to be made visible.

Basically rather than doing things from the oppo workflow, you halt things and wait for the other workflow to "unlock" the oppo workflow by adding the date into that hidden field. This means your visibility check simply checks for the existence of a date in that field. As this date field is not on any screen and is only updated by another workflow, there is no way for the user to move things forward without following the required process.

Some element of user training will be required on this.

Lee

Ok I have a significant amount of data on the custom table and it doesn't really require a workflow so what code should I be putting into my update script to put this "lock" into place?

I can call the current context and assign the check field to a variable no problems, I'm just unsure of the code that actually assigns the check data to the hidden field on the opportunity table.

Thanks

This line:

 oOppo = eWare.FindRecord("opportunity", "oppo_opportunityid=" + Values("resi_opportunityid")); // Look for the oppo

should be:

 var oOppo = eWare.FindRecord("opportunity", "oppo_opportunityid=" + Values("resi_opportunityid")); // Look for the oppo

Cheers,

Lee

Oops, and this:

if(resi_status == "active") // Is the status set to "active" - you need to define your conditions here


should be:

if(Values("resi_status") == "active") // Is the status set to "active" - you need to define your conditions here

Lee

Hi Lee,

That all makes perfect sense. I will have a crack at that first thing on Monday morning!

Cheers

Chris

I'll be back Tuesday :)

Lee

Hi Lee,

No joy I'm afraid! I have set up a checker field on th opportunity entity called oppo_rescheckfield of type "Text" and Length 1. The field used on the residence entity to determine if the record is "active" or not is called resi_residenceend.

The opportunity id is held in the SSA resi_admssionid.

So on updating the residence entity with the field resi_residenceend set to NULL the script does fire as I've had syntax error messages from my typos (now resolved) but the checkerfield isn't updated...

the only thing I can think of is that on the screen where the update takes place the actual SSA resi_admissionid displays a custom reference number, not the oppportunity id. However if I run a SQL select the resi_admissionid field does hold the opportunityid as it should.

Could this be the problem?

Thanks

function InsertRecord()
 
{
UpdateOpportunity()
  // Handle insert record actions here
 
}
 
 
function PostInsertRecord()
 
{
 
  // Handle post insert record actions here
 
}
 
 
function UpdateRecord()
 
{
UpdateOpportunity()
  // Handle update record actions here
 
}
 
 
function DeleteRecord()
 
{
 
  // Handle delete record actions here
 
}
 
function UpdateOpportunity()
{
if(Values("resi_residenceend") = "") // Is the status set to "active" - you need to define your conditions here
  {
    var oOppo = eWare.FindRecord("opportunity", "oppo_opportunityid=" + Values(resi_admissionid)); // Look for the oppo
 
    if(!oOppo.EOF) // Did we find it?
    {
      oOppo.oppo_rescheckfield = "x"; // Set the check field value to something
      oOppo.SaveChanges();  // Save the changes back
    }
  }
}

                                              

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:

This line:

if(Values("resi_residenceend") = "") // Is the status set to "active" - you need to define your conditions here

should be:

if(Values("resi_residenceend") == "") // Is the status set to "active" - you need to define your conditions here

See how that changes things.

Lee

Bingo! Sorry about that, I mistyped that bit. That has done the trick.

I have now put conditionals on the buttons in the workflow and all works brilliant. Thanks very much.

One quick query...how would I display a info message on the Oppo Summary screen to notify the user of something. I don't want to use an ErrorStr just a blue bar at the top if that's possible to say that this record is in progress and must be ended to reveal the workflow buttons?

Thanks

There is a way of doing it but it is long winded and requires a technique [sometimes] called the dummy field technique. It requires you to create a dummy 1 char text field and make it readonly. In the create script of the field you hijack the caption element and use that to inject HTML to put in a warning message and you can then set the style elements class to be CLASS=InfoContent. This will give you the blue bar in place of the caption. The field should be the first field on the screen and the second field should have a new line set before it. Then set the dummy field column width to match the number of columns you have on the screen.

See what I mean about being a bit of a pain? You should consider using the errorstr or just slapping the users hard enough until they get it.

Cheers,

Lee

Yeah that's a bit long winded. I think I'll go for your final option...should be more enjoyable than hooking up a dummy field ;-)

Thanks for your help on this one, I'll close it off and assign points.

Cheers

Chris