We plan to integrate with payment gateways soon. Until then, we will provide bank account details into which money has to be credited electronically. Payment will be quarterly in advance.
Appiyo can soon be downloaded as a mobile app from Google playstore and later from Apple istore. Until then, Appiyo can still be accessed using mobile browser.
When Appiyo is downloaded into a mobile, the device is connected to the Appiyo platform, thus enabling notifications. Notifications to non-members will have to be routed through a mobile SMS gateway using an appropriate SMS plan. This will have to be provisioned separately.
In an on-premise installation, the mobile must have access to the Net for notifications to work.
The preferred architecture is to have the database collocated in the cloud where Appiyo is operating. This will eliminate bandwidth consumption and also latency issues. Currently supported databases are MYSQL, MS SQL and Postgress. In the future, more databases will be supported. Appiyo plans to have strategic partnerships with cloud db vendors and cloud service providers in the future. This will create more choices for customers.
Currently Appiyo provides adapters to Salesforce, OpenERP, Alfresco, Facebook, Twitter, SMTP mail server and Web Services. REST APIs will be included soon. Appiyo plans to include more adapters progressively. Unique adapters and end-point connectors will have to be custom built by Appiyo.
Port-tunneling with required permissions will allow Appiyo to connect to end-points / datasources which reside behind firewalls. Alternately, an Appiyo listener can be installed behind the firewalls and can serve as a proxy between external Appiyo and internal datasources. The latter is presently unavailable and is included in the Appiyo roadmap for next release.
To enhance security while accessing Appiyo zones, IP range and device id based security features will be soon implemented in Appiyo. This will prevent unauthorized access.
Every Appiyo member is an owner of his/her community zone. Likewise a creator of a commercial zone will be the zone owner for that zone. Zone owners are de facto zone administrators who can operate their zones and assign privileges to zone members.
Date & Time stamps are important parameters for information about discussions and processes. Currently, Appiyo uses GMT of server and converts it to client (browser) time. Later, we plan to introduce preferred time zone in the user profile giving user a preference setting option.
Currently apps are restricted to operate in the zone in which they are created. In the future release, Appiyo will give import-export feature to enable movement of apps across zones. Marketplace will also become available in the future release from where apps can be sourced.
From the Marketplace (not available yet). Also, by using ‘explore’ option in ‘Applications’ menu.
Apps built in Appiyo will only run inside the Appiyo environment.
Yes, by invoking REST APIs to call workflows inside Appiyo. Custom UIs may have to be built separately outside Appiyo in such cases.
The zone administrator will have to decide what processapps have to be de-prioritized and un-deploy them to release container capacity. Or, the zone administrator can opt for a commercial zone.
This will happen if a workflow is improperly designed. Example, infinite loops can be a cause. If a zone container exceeds memory because of such reasons, the container will automatically get re-started. However, if the occurrence exceeds 10 times, then the zone will be blocked for audit. The zone administrator will have to get in touch with Appiyo support team.
Both deployment and execution of processapps will utilize container capacity more than the social component. The zone administrator will have to manage container capacity utilization in My Zone and opt for a commercial zone for processapps, if scale becomes necessary.
Data in Appiyo comprises many types. They are social related data such as discussions, photos, documents, etc., Process related data such as process instance information and apps related data (record data). There will be a 10 GB limit enforced on the volume of all data.