Best way to create an App from another App?

Follow

Callserver

• March 15, 2013 11:16

I might get some 'been there done that's' here, so that's why I am posting this.

We plan meetings. And each meeting has participants. Each meeting thus has an app with participants. They have some fields and categories. This app has webhooks to arrange email-messages and invoicing.

Adding an app for each meeting is a lot of work and setting up the webhook is not easy for non-tech people. So I created an app where you add meetings, with another webhook.

When a meeting is added, the webhook creates a new app, with the right fields, and the right webhook, and verifies the webhook (need to check if this is possible), so ready to use.

You would also be able to control it: archive or even delete it.

Has someone done this before? (By the way, would be great standard functionality...!) Sort of 'reverse app reference, by creating an app instead of an item). 

0

• 

  Casper Fabricius

  • March 15, 2013 11:31

  Why do you need a new app for each meeting? Why not just reuse the same participants app for all meetings? Or use the built-in participants functionality for meetings instead of having them in a separate app?

  0

  Comment actions Permalink
• 

  Callserver

  • March 15, 2013 12:29

  Because, for each participant and each meeting, we need to have payment status, email status. A meeting should have 'items' to provide this.

  Meeting

  • participant A
    
    PAYMENT: done  | not done
    
    EMAIL: done | not done

  • participant B
    
    PAYMENT: done  | not done
    
    EMAIL: done | not done

  • participant C
    
    PAYMENT: done  | not done
    
    EMAIL: done | not done

  • etc

  Since a participant can join more meetings, your suggestion is not working, or am I wrong?

   

  0

  Comment actions Permalink
• 

  Carl-Fredrik Herö

  • March 15, 2013 12:35

  I would have an app for meetings and another for participants. Then reference participants to the meeting using app reference-field.

  0

  Comment actions Permalink
• 

  Callserver

  • March 15, 2013 12:38

  Then again, how can I keep track of the payment and emailstatus per meeting for each participant?

   

  Because a participant would be an item in an app, I can do a lot more with them. The participants are workspace contacts now, that's how we set it up. 

   

  0

  Comment actions Permalink
• 

  Callserver

  • March 15, 2013 12:40

  This is how our Meeting-app with participants look like. The first column is a workspace contact.

   

  0

  Comment actions Permalink
• 

  Carl-Fredrik Herö

  • March 15, 2013 12:43

  That's the right way to do it, use workspace-contacts for regular user-info (like phone, email etc) and the participants app for different statuses. Each partipants item would be connected to an item in the meetings app.

  0

  Comment actions Permalink

Please sign in to leave a comment.