Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support v2 options when creating cases #7

Open
joeljunstrom opened this issue Jun 12, 2015 · 4 comments
Open

Support v2 options when creating cases #7

joeljunstrom opened this issue Jun 12, 2015 · 4 comments
Labels
Milestone

Comments

@joeljunstrom
Copy link

All new options when creating cases (including templateId and the new EventCallback structure)

https://app.egree.com/api#Createacase

@joeljunstrom joeljunstrom added this to the Egree API v2 milestone Jun 12, 2015
@jawa
Copy link
Contributor

jawa commented Jun 12, 2015

Is the CaseOptionsMapper needed or should all options go into the Case model? It seems like there is no clear distinction between the case and the options from the API documentation. Or should the required fields be considered part of the core case and the others as options?

@joeljunstrom
Copy link
Author

I guess we could make the distinction on the difference between what is sent wen creating a case and what is returned when receiving one from the api? (If any)

@joeljunstrom
Copy link
Author

But if you feel that the distinction does not add clarity or is unnecessary feel free to change it

@jawa
Copy link
Contributor

jawa commented Jun 12, 2015

No, that sounds reasonable to have the response of getcase to act as the base of the case so to speak :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants