# Campaign Creation & Management System #

**Note**: this documentation is in ongoing state

This Project will help to create and execute the campaign. To simplify our process flow
we have considered Campaign as series of functions. Each function depends on the previous input. And compulsory gives output

### Function ###

* Fields required JSON schema
* Output JSON schema
* Trigger
* Action
* Fetch (internal to function)

f(defaultInputFromUI, previousFunctionOutput) => output + mutation (like sending email, sms, pushnotification etc.)

### Transducer Function ###

Each function will have a different type of input and different type of output.
It will just convert the data structure of input to desired structure.


### Cron ###

Cron task will check constraint of the process and execute as per input.

### Database Structure ###

* campaign
	* campaign_id
	* desciption
	* start_timestamp
	* end_timestamp
* process
	* campaign_id
	* default_input
	* input
	* reference_process_id
	* output
	* function_name
	* transducer_name (convert input to differnt output, default null)
	* schedule (e.g. daily at 5:30 in cron format or other format)
	* start_timestamp
	* end_timestamp (e.g. every process should have limit.)
	* state: enum(started, running, pending) useful if process failed
* notification (will be used to notify fronend user)
	* notification_id
	* type
	* notification_data
	* read (default false)
	* read_timesatmp