PRICING

HELP

BLOG

APPSTORE

COMPANY

LEGAL

LOGIN

AI Assisted Content Management System

Analytics & Lead Generation

Automation Projects

Browser Extension Apps

Dashboard Theme Analysis: LN1

Data Exchange Automation Tools

Getting Started With Building Hybrid Apps

Izyware Hybrid UX Design Guidelines

Legacy Features and Backward Compatibility

How does the legacy frame architecture work

Izyware Legacy UI Circus Engine

Case Studies and Knowledge Center

Build and deploy a content distribution app in less than five minutes: Part II

Comparison of CSS Preprocessors SASS vs LESS vs STYLUS

Comparison of node.js test frameworks and utilities: lab, chai, sinon

Manage and automate your day to day business tools using IzyCloud Tasks: Part I

MySql Performance Optimization

Onboarding Tutorial: Creating & publishing an app

Rebranding and Customizing Websites

Using IzyCloud on Android: IzyCloud Query App

Technical Resources

.NET SDKCore IzyWare

accounts README

ElasticSearch IzyWare Data Console Feature

End To End Testing

End To End Testing, Part II

frames and nav (ui/w/shell/navmulti) README

izy-circus README

izy-idman-tools README

izy-pop3 README

izy-proxy README

izy-sync README

IzyIDE README

IzyShell readme

ReKey Feature Package README for IzyWare SQL Console

Tasks Migration : V5 guidelines

V5 Migration : apps/pulse guidelines README

Container Orchestration

Izy Kubernetes Internal Networking Troubleshooting

Application Hosting

Content Publisher

Domain Registration

Email Hosting

Izyware Browser Extension

Izyware Deployment Engine

Izyware Session Management

Messaging System APIs and functionality

Single SignOn

Integration APIs

AWS SDK

Azure and .NET

<< Izyware Session Management

Single SignOn >>

Messaging System APIs and functionality

Messaging System APIs and functionality

Functionality

• Generate content (email subjects, body, etc.) using scripted templtes
• Deliver messages using the Transfer Agent for the specific message type
• Keep a log of all the messages exchanged in the system

Scripting Signature

You may launch the API by doing:

['//executioncontext/messaging:viewer/compose/api/crud', payload, modtask]

The outcome will be put in modtask.outcome, i.e.

launchAPI(payload, cb) => {

doChain([

['//executioncontext/messaging:viewer/compose/api/crud', payload, modtask],

() => cb(modtask.outcome)

])

}

Actions

Generate

Payload should be

{

action: 'generate',

objconfig: {

templateaddress: 'the-template-address',

fromIds: [userId, ...]

toIds: [userIdm ...]

}

}

And the output will create a JSON representation of the messagelog entry:

{

success: true,

data: {

fromId: obj.froms[0].id,

fromEmail: obj.froms[0].user,

toId: obj.tos[0].id,

toEmail: obj.tos[0].user,

subject: obj.template.title,

body: obj.template.description,

templatepath: objconfig.templateaddress

}

}

process

Will either create a new messagelog entry and call the transfer agent or load an existing messagelog entry and call the transfer agent.

If the payload is

{

action: 'process',

obj: {

// outcome.data from the call to generate

}

}

then the API will generate a new messagelog entry. However, if the payload is:

{

action: 'process',

messageId: numeric value

}

the API will load the messagelog entry based on messageId.

In both cases the API will send a using the transfer agent.