Skip to main content
Salesforce

Return to Answer

added 86 characters in body
Source Link
Guy Clairbois
Guy Clairbois
  • 10.8k
  • 32
  • 54

Most of the objects that represent a Flow have key prefixes starting at 300 and going through to 31v.

E.g.

  • 300 InteractionDefinition
  • 301 InteractionDefinitionVersion
  • 308 InteractionCondition

None of these currently (Spring 14 / v30.0) appear to be accessible via the Partner API, the tooling API, or directly in Apex. They don't appear in the sObjects returned by a REST GET to /services/data/v30.0/sobjects or /services/data/v30.0/tooling/sobjects.

In Apex you can see the SObjectType, but that is about it.

Schema.SObjectType r = Id.valueOf('300100000000000').getSObjectType();
System.debug(r); // Debugs as InteractionDefinition

I'd say the Metadata API is currently your best option (e.g. via SFDC workbench):

Flows in the Metadata API

Most of the objects that represent a Flow have key prefixes starting at 300 and going through to 31v.

E.g.

  • 300 InteractionDefinition
  • 301 InteractionDefinitionVersion
  • 308 InteractionCondition

None of these currently (Spring 14 / v30.0) appear to be accessible via the Partner API, the tooling API, or directly in Apex. They don't appear in the sObjects returned by a REST GET to /services/data/v30.0/sobjects or /services/data/v30.0/tooling/sobjects.

In Apex you can see the SObjectType, but that is about it.

Schema.SObjectType r = Id.valueOf('300100000000000').getSObjectType();
System.debug(r); // Debugs as InteractionDefinition

I'd say the Metadata API is currently your best option:

Flows in the Metadata API

Most of the objects that represent a Flow have key prefixes starting at 300 and going through to 31v.

E.g.

  • 300 InteractionDefinition
  • 301 InteractionDefinitionVersion
  • 308 InteractionCondition

None of these currently (Spring 14 / v30.0) appear to be accessible via the Partner API, the tooling API, or directly in Apex. They don't appear in the sObjects returned by a REST GET to /services/data/v30.0/sobjects or /services/data/v30.0/tooling/sobjects.

In Apex you can see the SObjectType, but that is about it.

Schema.SObjectType r = Id.valueOf('300100000000000').getSObjectType();
System.debug(r); // Debugs as InteractionDefinition

I'd say the Metadata API is currently your best option (e.g. via SFDC workbench):

Flows in the Metadata API

added 300 characters in body
Source Link
Daniel Ballinger
Daniel Ballinger
  • 103k
  • 40
  • 275
  • 601

Most of the objects that represent a Flow have key prefixes starting at 300 and ending ingoing through to 31v.

E.g.

  • 300 InteractionDefinition
  • 301 InteractionDefinitionVersion
  • 308 InteractionCondition

None of these currently (Spring 14 / v30.0) appear to be accessible via the Partner API, the tooling API, or directly in Apex. They don't appear in the sObjects returned by a REST GET to /services/data/v30.0/sobjects or /services/data/v30.0/tooling/sobjects.

In Apex you can see the SObjectType, but that is about it.

Schema.SObjectType r = Id.valueOf('300100000000000').getSObjectType();
System.debug(r); // Debugs as InteractionDefinition

I'd say the Metadata API is currently your best option:

Flows in the Metadata API

Most of the objects that represent a Flow have key prefixes starting at 300 and ending in 31v.

E.g.

  • 300 InteractionDefinition
  • 301 InteractionDefinitionVersion
  • 308 InteractionCondition

None of these currently appear to be accessible via the Partner API, the tooling API, or directly in Apex.

In Apex you can see the SObjectType, but that is about it.

Schema.SObjectType r = Id.valueOf('300100000000000').getSObjectType();
System.debug(r); // Debugs as InteractionDefinition

Most of the objects that represent a Flow have key prefixes starting at 300 and going through to 31v.

E.g.

  • 300 InteractionDefinition
  • 301 InteractionDefinitionVersion
  • 308 InteractionCondition

None of these currently (Spring 14 / v30.0) appear to be accessible via the Partner API, the tooling API, or directly in Apex. They don't appear in the sObjects returned by a REST GET to /services/data/v30.0/sobjects or /services/data/v30.0/tooling/sobjects.

In Apex you can see the SObjectType, but that is about it.

Schema.SObjectType r = Id.valueOf('300100000000000').getSObjectType();
System.debug(r); // Debugs as InteractionDefinition

I'd say the Metadata API is currently your best option:

Flows in the Metadata API

added 194 characters in body
Source Link
Daniel Ballinger
Daniel Ballinger
  • 103k
  • 40
  • 275
  • 601

Most of the objects that represent a Flow have key prefixes starting at 300 and ending in 31v.

E.g.

  • 300 InteractionDefinition
  • 301 InteractionDefinitionVersion
  • 308 InteractionCondition

None of these currently appear to be accessible via the Partner API, the tooling API, or directly in Apex.

In Apex you can see the SObjectType, but that is about it.

Schema.SObjectType r = Id.valueOf('300100000000000').getSObjectType();
System.debug(r); // Debugs as InteractionDefinition

Most of the objects that represent a Flow have key prefixes starting at 300 and ending in 31v.

E.g.

  • 300 InteractionDefinition
  • 301 InteractionDefinitionVersion
  • 308 InteractionCondition

None of these currently appear to be accessible via the Partner API, the tooling API, or directly in Apex.

Most of the objects that represent a Flow have key prefixes starting at 300 and ending in 31v.

E.g.

  • 300 InteractionDefinition
  • 301 InteractionDefinitionVersion
  • 308 InteractionCondition

None of these currently appear to be accessible via the Partner API, the tooling API, or directly in Apex.

In Apex you can see the SObjectType, but that is about it.

Schema.SObjectType r = Id.valueOf('300100000000000').getSObjectType();
System.debug(r); // Debugs as InteractionDefinition
Source Link
Daniel Ballinger
Daniel Ballinger
  • 103k
  • 40
  • 275
  • 601