Best way to create an App from another App?

Comments

6 comments

  • Casper Fabricius

    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

    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ö

    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

    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

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

     

    0
    Comment actions Permalink
  • Carl-Fredrik Herö

    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.

Powered by Zendesk