[jira] [Commented] (FINERACT-26) Allow a Logo (for Organization) to be set, which will be displayed on the header
[ https://issues.apache.org/jira/browse/FINERACT-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16972712#comment-16972712 ] Abhay Chawla commented on FINERACT-26: -- [~awasum] This is a backend issue. There is a need to create an API so the logo can be made configurable, saved at the server end and used within the application for all its users. Once the API is developed it will be used in the front end to implement the functionality that is to upload a logo and retrieve it to display within the application. A corresponding issue for the same is already there on the web app. > Allow a Logo (for Organization) to be set, which will be displayed on the > header > > > Key: FINERACT-26 > URL: https://issues.apache.org/jira/browse/FINERACT-26 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Minor > Labels: 2019-mifos-gsoc, gsoc, p1 > Fix For: 1.4.0 > > > https://mifosforge.jira.com/browse/MIFOSX-2511 > As a Implementation Specialist, I wish to setup a logo (for the organization) > which will be displayed before the Mifos logo > As a first step : there is no user interface needed for uploading the logo. > As a second step : we can provide user interface for logo-upload > Logo can be different for different tenants (in a multi-tenant setup). > Logo should be same size as Mifos X logo - to maintain aesthetics of the > header band. > Part 2 ] While we are at it, we should probably also allow themes to be > picked on on a per tenant basis -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (FINERACT-26) Allow a Logo (for Organization) to be set, which will be displayed on the header
[ https://issues.apache.org/jira/browse/FINERACT-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16713133#comment-16713133 ] Abhay Chawla edited comment on FINERACT-26 at 12/7/18 5:54 PM: --- Reference: https://issues.apache.org/jira/browse/FINERACT-638 1) Support for saving and retrieving the Name of the Organisation, Description, Summary, Default Language, Default Date Format 2) Support for saving and retrieving images including Favicon, Cover Image, Organisation Logo, Organisation Logo with Name 3) Support for saving and retrieving Default theme and font to be used within the application 4) Support for saving and retrieving contact information including website, email, contact no (multiple if required) App configuration for the new web app will be based on the Tenant, the following things can be saved or modified by the permitted administrators within the organization only from the available user interface once they are logged in (when authenticated), however, everything will be retrievable without the need of authentication from the login page itself based on the Tenant so that it can be shown there as well. If need and as mentioned here, we can specify the dimensions of the specific logo/images as well to ensure it looks the best when used. was (Author: abhaychawla): Reference: https://issues.apache.org/jira/browse/FINERACT-638?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel=16712351#comment-16712351 1) Support for saving and retrieving the Name of the Organisation, Description, Summary, Default Language, Default Date Format 2) Support for saving and retrieving images including Favicon, Cover Image, Organisation Logo, Organisation Logo with Name 3) Support for saving and retrieving Default theme and font to be used within the application 4) Support for saving and retrieving contact information including website, email, contact no (multiple if required) App configuration for the new web app will be based on the Tenant, the following things can be saved or modified by the permitted administrators within the organization only from the available user interface once they are logged in (when authenticated), however, everything will be retrievable without the need of authentication from the login page itself based on the Tenant so that it can be shown there as well. If need and as mentioned here, we can specify the dimensions of the specific logo/images as well to ensure it looks the best when used. > Allow a Logo (for Organization) to be set, which will be displayed on the > header > > > Key: FINERACT-26 > URL: https://issues.apache.org/jira/browse/FINERACT-26 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p1 > Fix For: 1.3.0 > > > https://mifosforge.jira.com/browse/MIFOSX-2511 > As a Implementation Specialist, I wish to setup a logo (for the organization) > which will be displayed before the Mifos logo > As a first step : there is no user interface needed for uploading the logo. > As a second step : we can provide user interface for logo-upload > Logo can be different for different tenants (in a multi-tenant setup). > Logo should be same size as Mifos X logo - to maintain aesthetics of the > header band. > Part 2 ] While we are at it, we should probably also allow themes to be > picked on on a per tenant basis -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (FINERACT-26) Allow a Logo (for Organization) to be set, which will be displayed on the header
[ https://issues.apache.org/jira/browse/FINERACT-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16713133#comment-16713133 ] Abhay Chawla edited comment on FINERACT-26 at 12/7/18 5:55 PM: --- Reference: https://issues.apache.org/jira/browse/FINERACT-638 1) Support for saving and retrieving the Name of the Organisation, Description, Summary, Default Language, Default Date Format 2) Support for saving and retrieving images including Favicon, Cover Image, Organisation Logo, Organisation Logo with Name 3) Support for saving and retrieving Default theme and font to be used within the application 4) Support for saving and retrieving contact information including website, email, contact no (multiple if required) App configuration for the new web app will be based on the Tenant, the following things can be saved or modified by the permitted administrators within the organization only from the available user interface once they are logged in (when authenticated), however, everything will be retrievable without the need of authentication from the login page itself based on the Tenant so that it can be shown there as well. By default information related to Mifos will be visible. If needed as mentioned here, we can specify the dimensions of the specific logo/images as well to ensure it looks the best when used. was (Author: abhaychawla): Reference: https://issues.apache.org/jira/browse/FINERACT-638 1) Support for saving and retrieving the Name of the Organisation, Description, Summary, Default Language, Default Date Format 2) Support for saving and retrieving images including Favicon, Cover Image, Organisation Logo, Organisation Logo with Name 3) Support for saving and retrieving Default theme and font to be used within the application 4) Support for saving and retrieving contact information including website, email, contact no (multiple if required) App configuration for the new web app will be based on the Tenant, the following things can be saved or modified by the permitted administrators within the organization only from the available user interface once they are logged in (when authenticated), however, everything will be retrievable without the need of authentication from the login page itself based on the Tenant so that it can be shown there as well. If need and as mentioned here, we can specify the dimensions of the specific logo/images as well to ensure it looks the best when used. > Allow a Logo (for Organization) to be set, which will be displayed on the > header > > > Key: FINERACT-26 > URL: https://issues.apache.org/jira/browse/FINERACT-26 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Minor > Labels: gsoc, p1 > Fix For: 1.3.0 > > > https://mifosforge.jira.com/browse/MIFOSX-2511 > As a Implementation Specialist, I wish to setup a logo (for the organization) > which will be displayed before the Mifos logo > As a first step : there is no user interface needed for uploading the logo. > As a second step : we can provide user interface for logo-upload > Logo can be different for different tenants (in a multi-tenant setup). > Logo should be same size as Mifos X logo - to maintain aesthetics of the > header band. > Part 2 ] While we are at it, we should probably also allow themes to be > picked on on a per tenant basis -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (FINERACT-638) Creation of API's for Web App and Self Service Admin Portal
[ https://issues.apache.org/jira/browse/FINERACT-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16630217#comment-16630217 ] Abhay Chawla edited comment on FINERACT-638 at 9/27/18 11:16 AM: - [~Shruthi M R], In the issue tickets already mentioned above, you would be able to see the complete requirements along with the proposed UI for the same which contains the fields that are required for the given operation. For the self-service user management creation, the current API allows the clients themselves to activate their accounts via the web-self-service app and the mobile app, but for this, we require to allow the administrators i.e. the financial institution to create a self-service account for an existing client or create a self-service account for a new client. So I think we require separate APIs for the same. was (Author: abhaychawla): [~Shruthi M R], In the issue tickets already mentioned above, you would be able to see the complete requirements along with the proposed UI for the same which contains the fields that are required for the required operation. For the self-service user management creation, the current API allows the clients themselves to activate their accounts via the web-self-service app and the mobile app, but for this, we require to allow the administrators i.e. the financial institution to create a self-service account for an existing client or create a self-service account for a new client. So I think we require separate APIs for the same. > Creation of API's for Web App and Self Service Admin Portal > --- > > Key: FINERACT-638 > URL: https://issues.apache.org/jira/browse/FINERACT-638 > Project: Apache Fineract > Issue Type: New Feature > Components: Organization, System, User Management >Reporter: Abhay Chawla >Assignee: Shruthi M R >Priority: Major > Labels: gsoc, p1 > > List of API's that will be required are as follows- > App Configuration for the new web app, based on the Tenant so that they can > be accessed on the login page itself before authentication: > 1) Support for saving and retrieving the Name of the Organisation, > Description, Summary, Default Language, Default Date Format > 2) Support for saving and retrieving images including Favicon, Cover Image, > Organisation Logo, Organisation Logo with Name > 3) Support for saving and retrieving Default theme and font to be used within > the application > 4) Support for saving and retrieving contact information including website, > email, contact no (multiple if required) > App Configuration for the self-service mobile app and online banking app, > based on Tenant so that they can be accessed on the login page itself before > authentication: > 5) Support for saving and retrieving the Name of the Organisation, > Description, Summary, Default Language, Default Date Format (common) > 6) Support for saving and retrieving images including Favicon, Cover Image, > Organisation Logo, Organisation Logo with Name (common and will be used as > required by whichever application) > 7) Support for saving and retrieving Default theme and font to be used within > the application (separate for mobile and online banking app) > 8) Support for saving and retrieving contact information including website, > email, contact no (common, multiple if required) > Self Service User Management and Creation > 1) Support for viewing current and potential self-service users. > 2) Support for activating and deactivating self-service users (single and > bulk). > 3) Support for creating new self-service users. > 4) Support for viewing, editing and changing the password of a self-service > user. > Refer to Issues: > https://github.com/openMF/web-app/issues/33 > https://github.com/openMF/web-app/issues/34 > https://github.com/openMF/web-app/issues/35 > https://github.com/openMF/web-app/issues/36 > Self Service JIRA Link: > https://mifosforge.jira.com/wiki/spaces/MIFOSX/pages/102629583/Customer+Self+Service -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (FINERACT-638) Creation of API's for Web App and Self Service Admin Portal
[ https://issues.apache.org/jira/browse/FINERACT-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16630217#comment-16630217 ] Abhay Chawla edited comment on FINERACT-638 at 9/27/18 11:14 AM: - [~Shruthi M R], In the issue tickets already mentioned above, you would be able to see the complete requirements along with the proposed UI for the same which contains the fields that are required for the required operation. For the self-service user management creation, the current API allows the clients themselves to activate their accounts via the web-self-service app and the mobile app, but for this, we require to allow the administrators i.e. the financial institution to create a self-service account for an existing client or create a self-service account for a new client. So I think we require separate APIs for the same. was (Author: abhaychawla): [~Shruthi M R], In the issue tickets already mentioned above, you would be able to see the complete requirements along with the proposed UI for the same which contains the fields that are required for the required operation. For the self-service user management creation, the current API allows the clients themselves to activate their accounts via the web-self-service app and the mobile app, but for this, we require to allow the administrators i.e. the financial institution to create a self-service account for an existing client or create a self-service account for a new client. > Creation of API's for Web App and Self Service Admin Portal > --- > > Key: FINERACT-638 > URL: https://issues.apache.org/jira/browse/FINERACT-638 > Project: Apache Fineract > Issue Type: New Feature > Components: Organization, System, User Management >Reporter: Abhay Chawla >Assignee: Shruthi M R >Priority: Major > Labels: gsoc, p1 > > List of API's that will be required are as follows- > App Configuration for the new web app, based on the Tenant so that they can > be accessed on the login page itself before authentication: > 1) Support for saving and retrieving the Name of the Organisation, > Description, Summary, Default Language, Default Date Format > 2) Support for saving and retrieving images including Favicon, Cover Image, > Organisation Logo, Organisation Logo with Name > 3) Support for saving and retrieving Default theme and font to be used within > the application > 4) Support for saving and retrieving contact information including website, > email, contact no (multiple if required) > App Configuration for the self-service mobile app and online banking app, > based on Tenant so that they can be accessed on the login page itself before > authentication: > 5) Support for saving and retrieving the Name of the Organisation, > Description, Summary, Default Language, Default Date Format (common) > 6) Support for saving and retrieving images including Favicon, Cover Image, > Organisation Logo, Organisation Logo with Name (common and will be used as > required by whichever application) > 7) Support for saving and retrieving Default theme and font to be used within > the application (separate for mobile and online banking app) > 8) Support for saving and retrieving contact information including website, > email, contact no (common, multiple if required) > Self Service User Management and Creation > 1) Support for viewing current and potential self-service users. > 2) Support for activating and deactivating self-service users (single and > bulk). > 3) Support for creating new self-service users. > 4) Support for viewing, editing and changing the password of a self-service > user. > Refer to Issues: > https://github.com/openMF/web-app/issues/33 > https://github.com/openMF/web-app/issues/34 > https://github.com/openMF/web-app/issues/35 > https://github.com/openMF/web-app/issues/36 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-638) Creation of API's for Web App and Self Service Admin Portal
[ https://issues.apache.org/jira/browse/FINERACT-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16630217#comment-16630217 ] Abhay Chawla commented on FINERACT-638: --- [~Shruthi M R], In the issue tickets already mentioned above, you would be able to see the complete requirements along with the proposed UI for the same which contains the fields that are required for the required operation. For the self-service user management creation, the current API allows the clients themselves to activate their accounts via the web-self-service app and the mobile app, but for this, we require to allow the administrators i.e. the financial institution to create a self-service account for an existing client or create a self-service account for a new client. > Creation of API's for Web App and Self Service Admin Portal > --- > > Key: FINERACT-638 > URL: https://issues.apache.org/jira/browse/FINERACT-638 > Project: Apache Fineract > Issue Type: New Feature > Components: Organization, System, User Management >Reporter: Abhay Chawla >Assignee: Shruthi M R >Priority: Major > Labels: gsoc, p1 > > List of API's that will be required are as follows- > App Configuration for the new web app, based on the Tenant so that they can > be accessed on the login page itself before authentication: > 1) Support for saving and retrieving the Name of the Organisation, > Description, Summary, Default Language, Default Date Format > 2) Support for saving and retrieving images including Favicon, Cover Image, > Organisation Logo, Organisation Logo with Name > 3) Support for saving and retrieving Default theme and font to be used within > the application > 4) Support for saving and retrieving contact information including website, > email, contact no (multiple if required) > App Configuration for the self-service mobile app and online banking app, > based on Tenant so that they can be accessed on the login page itself before > authentication: > 5) Support for saving and retrieving the Name of the Organisation, > Description, Summary, Default Language, Default Date Format (common) > 6) Support for saving and retrieving images including Favicon, Cover Image, > Organisation Logo, Organisation Logo with Name (common and will be used as > required by whichever application) > 7) Support for saving and retrieving Default theme and font to be used within > the application (separate for mobile and online banking app) > 8) Support for saving and retrieving contact information including website, > email, contact no (common, multiple if required) > Self Service User Management and Creation > 1) Support for viewing current and potential self-service users. > 2) Support for activating and deactivating self-service users (single and > bulk). > 3) Support for creating new self-service users. > 4) Support for viewing, editing and changing the password of a self-service > user. > Refer to Issues: > https://github.com/openMF/web-app/issues/33 > https://github.com/openMF/web-app/issues/34 > https://github.com/openMF/web-app/issues/35 > https://github.com/openMF/web-app/issues/36 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-638) Creation of API's for Web App and Self Service Admin Portal
[ https://issues.apache.org/jira/browse/FINERACT-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhay Chawla updated FINERACT-638: -- Description: List of API's that will be required are as follows- App Configuration for the new web app, based on the Tenant so that they can be accessed on the login page itself before authentication: 1) Support for saving and retrieving the Name of the Organisation, Description, Summary, Default Language, Default Date Format 2) Support for saving and retrieving images including Favicon, Cover Image, Organisation Logo, Organisation Logo with Name 3) Support for saving and retrieving Default theme and font to be used within the application 4) Support for saving and retrieving contact information including website, email, contact no (multiple if required) App Configuration for the self-service mobile app and online banking app, based on Tenant so that they can be accessed on the login page itself before authentication: 5) Support for saving and retrieving the Name of the Organisation, Description, Summary, Default Language, Default Date Format (common) 6) Support for saving and retrieving images including Favicon, Cover Image, Organisation Logo, Organisation Logo with Name (common and will be used as required by whichever application) 7) Support for saving and retrieving Default theme and font to be used within the application (separate for mobile and online banking app) 8) Support for saving and retrieving contact information including website, email, contact no (common, multiple if required) Self Service User Management and Creation 1) Support for viewing current and potential self-service users. 2) Support for activating and deactivating self-service users (single and bulk). 3) Support for creating new self-service users. 4) Support for viewing, editing and changing the password of a self-service user. Refer to Issues: https://github.com/openMF/web-app/issues/33 https://github.com/openMF/web-app/issues/34 https://github.com/openMF/web-app/issues/35 https://github.com/openMF/web-app/issues/36 was: List of API's that will be required are as follows- App Configuration for the new web app, based on the Tenant so that they can be accessed on the login page itself before authentication: 1) Support for saving and retrieving the Name of the Organisation, Description, Summary, Default Language, Default Date Format 2) Support for saving and retrieving images including Favicon, Cover Image, Organisation Logo, Organisation Logo with Name 3) Support for saving and retrieving Default theme and font to be used within the application 4) Support for saving and retrieving contact information including website, email, contact no (multiple if required) App Configuration for the self-service mobile app and online banking app, based on Tenant so that they can be accessed on the login page itself before authentication: 5) Support for saving and retrieving the Name of the Organisation, Description, Summary, Default Language, Default Date Format (common) 6) Support for saving and retrieving images including Favicon, Cover Image, Organisation Logo, Organisation Logo with Name (common and will be used as required by whichever application) 7) Support for saving and retrieving Default theme and font to be used within the application (separate for mobile and online banking app) 8) Support for saving and retrieving contact information including website, email, contact no (common, multiple if required) Refer to Issues: https://github.com/openMF/web-app/issues/35 https://github.com/openMF/web-app/issues/36 Component/s: (was: Savings) Summary: Creation of API's for Web App and Self Service Admin Portal (was: Creation of API's for Self Service Admin Portal) > Creation of API's for Web App and Self Service Admin Portal > --- > > Key: FINERACT-638 > URL: https://issues.apache.org/jira/browse/FINERACT-638 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Abhay Chawla >Assignee: Shruthi M R >Priority: Major > Labels: gsoc, p1 > > List of API's that will be required are as follows- > App Configuration for the new web app, based on the Tenant so that they can > be accessed on the login page itself before authentication: > 1) Support for saving and retrieving the Name of the Organisation, > Description, Summary, Default Language, Default Date Format > 2) Support for saving and retrieving images including Favicon, Cover Image, > Organisation Logo, Organisation Logo with Name > 3) Support for saving and retrieving Default theme and font to be used within > the application > 4) Support for saving and retrieving contact information including website, > email, contact no (multiple if required) > App Configuration for
