You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some users might want to host Raven on a separate server and not on the main server running ERPNext for performance reasons.
It makes sense to have an option to be able to refer to documents, view leave status of users, apply message actions, or run AI integrations on Raven and be connected to a separate server for them. To ensure user security, we might need to setup OAuth - a plain API key will not work since each user would have different rights on the main ERP server.
Not all features can work this way though - for example, sending a Raven would not work from ERPNext to Raven unless we have a lightweight "adapter" app installed in the ERPNext server for this. Timeline component and in-ERP chat would also need some sort of adapter. Maybe not needed for the first phase.
We might want to think about this.
The text was updated successfully, but these errors were encountered:
Some users might want to host Raven on a separate server and not on the main server running ERPNext for performance reasons.
It makes sense to have an option to be able to refer to documents, view leave status of users, apply message actions, or run AI integrations on Raven and be connected to a separate server for them. To ensure user security, we might need to setup OAuth - a plain API key will not work since each user would have different rights on the main ERP server.
Not all features can work this way though - for example, sending a Raven would not work from ERPNext to Raven unless we have a lightweight "adapter" app installed in the ERPNext server for this. Timeline component and in-ERP chat would also need some sort of adapter. Maybe not needed for the first phase.
We might want to think about this.
The text was updated successfully, but these errors were encountered: