Is there any documentation about how daylite:// can be used? Can it be used to activate menu items and such? Is it limited to daylite://ShowObject...

Thanks.

quote:

daylite://

Great question. Now we wait for market circle to respond.

This message has been edited. Last edited by: Andrew Migliore,

What I've found so far:

daylite://OpenEAddress/ID=nnn
daylite://ShowObject/?Entity=eee&ID=nnn
daylite://DialPhone/?ID=nnn

OpenEAddress appears to open the dialog for the object using defaultElectronicAddress.eAddressID

ShowObject brings up the dialog for the object specified in ID. It appears that the ID number space is reused that is you can have a Contact with an ID of 1000 and an Organization with an ID of 1000. To distinguish the name you specify the Entity name e.g. Contact, Organization, Project etc. in coding a HUD you would use model.entity.name

The DialPhone I assume does just that... using the phoneID of whatever defaultPhone or defaultSecondPhone you use.

cheers

Hey thanks Andrew. That's great information. I am glad someone out there reads these posts.

I believe there is more and all of this should be documented somewhere and made available to developers (Market Circle?).

For example there must be a way of openning a "new" dialog for a contact etc. and populate it ala DMI.

I also found this syntax in the help docs. This may have some potential. I guess it really depends on the implementation.

daylite3:/?Command=OpenPreference&PaneIdentifier=GWFormsFieldsPreferenceClient&TabIdentifier=GWCustomRecordSetDefinitionUtility

Where exactly did you find the syntax in the help?

It also looks like the syntax is incorrect to me .... missing a slash?

Thanks.

You know, I noticed that too. In Help, I believe under the topic of Forms, there is a link that will open that specific Daylite preference panel. I just Control clicked and copied the link... This seems to be the only type of command in the Help files that I could find.

I sure wish Marketcircle would document this. It would really make HUD's a lot more powerful.

Thanks,
Isaac

Yes seems the single / (slash) is intentional. Here are some more.

daylite3:/?Command=OpenPreference&PaneIdentifier=GWAutoDialerPreferenceClient
daylite3:/?Command=OpenPreference&PaneIdentifier=GWClassificationPreferenceClient&TabIdentifier=GWCategoriesList
daylite3:/?Command=OpenPreference&PaneIdentifier=GWDefaultValuesPreferenceClient
daylite3:/?Command=OpenPreference&PaneIdentifier=GWFormsFieldsPreferenceClient&TabIdentifier=GWCustomRecordSetDefinitionUtility
daylite3:/?Command=OpenPreference&PaneIdentifier=GWLaunchPreferenceClient
daylite3:/?Command=OpenPreference&PaneIdentifier=GWOBDatabaseCombinedPreferenceClient
daylite3:/?Command=OpenPreference&PaneIdentifier=GWPipelinesPreferenceClient
daylite3:/?Command=OpenPreference&PaneIdentifier=GWSalesPreferenceClient&TabIdentifier=GWOpportunityStateReasonUtility
daylite3:/?Command=OpenPreference&PaneIdentifier=GWSalesPreferenceClient&TabIdentifier=GWOpportunityTypeUtility

So the hierarchy is Command -> PaneIdentifier -> TabIdentifier. I assume this format works with any dialog.

These names probably match up to the internal names of the classes in the API.