{"id":13185,"date":"2023-05-06T00:35:27","date_gmt":"2023-05-06T04:35:27","guid":{"rendered":"https:\/\/buzapps.net\/info\/?post_type=knowledgebase&p=13185"},"modified":"2024-07-16T14:36:43","modified_gmt":"2024-07-16T18:36:43","slug":"crm-data-manager-2","status":"publish","type":"knowledgebase","link":"https:\/\/buzapps.net\/info\/knowledgebase\/app-features\/crm-data-manager-2\/","title":{"rendered":"CRM (Data Manager)"},"content":{"rendered":"\n

The CRM Data Manager is a powerful information management system that enables you to manage and coordinate various sets of data with an easy to use, front-end user interface.<\/p>\n\n\n\n

Our CRM works in conjunction with our Awesome Forms feature<\/a><\/strong>. Via Awesome Forms, the data submitted via your Forms is easily managed. You’re able to view the information in the app, and link the various sets of submitted data. In addition, the CRM enables you to easily select the methods in which you want the data linked, and you can filter the information as you see fit.<\/p>\n\n\n\n

USE CASE:<\/strong><\/p>\n\n\n\n

A training school is a perfect example to help you understand how data can be coordinated using our CRM.<\/p>\n\n\n\n

Our CRM would enable you to create a School (or multiple schools), then add Classes to the School. Next, you can add Teachers data, and link the Teachers to the Classes.<\/p>\n\n\n\n

After the Class and Teacher information is linked, you would add Student data, and link the Students to the Classes. Lastly, Grades and Attendance data can be linked to the Students. Via the Query\/Reports functionality, one could create and display Reports in the app that show Grades and\/or Attendance levels per Class in the School. Likewise, you could easily see a Student’s Grades from their various Classes.<\/p>\n\n\n\n

The above scenario is a small example of the power of our CRM.\u00a0What makes it exceptional is the App Owner can easily create these relationships and link the data in an easy to use interface, without needing to hire a programmer to setup and manage their information.<\/p>\n\n\n\n

<\/div>\n\n\n\n

CREATE YOUR FORMS<\/h3>\n\n\n\n

If not already, create your required Forms using our Awesome Forms feature<\/strong>.\u00a0Click here<\/strong><\/a> for instructions<\/strong> on using Awesome Forms.<\/p>\n\n\n\n

<\/div>\n\n\n\n

GETTING STARTED<\/h3>\n\n\n\n

1)<\/strong> Log into your\u00a0App Manager<\/strong>\u00a0and\u00a0select your app<\/strong>.<\/p>\n\n\n\n

2)<\/strong> Click Features<\/strong> from the left-hand-side of the screen (or the middle of the screen).<\/p>\n\n\n\n

3)<\/strong>\u00a0Click\u00a0CRM <\/strong>(or whatever is the name of your Data Manager).<\/p>\n\n\n\n

<\/div>\n\n\n\n

ENTER COMPANY INFORMATION<\/h3>\n\n\n\n

1)<\/strong> Click the blue + button<\/strong> on the right-hand-side of the screen to add a Company<\/strong>.<\/p>\n\n\n\n

2)<\/strong> Add the Company information <\/strong>and select if the Company should be Published<\/strong> (live) or Draft<\/strong> (disabled).<\/p>\n\n\n\n

<\/div>\n\n\n\n

USER MANAGEMENT<\/h3>\n\n\n\n

ROLES<\/strong><\/p>\n\n\n\n

1)<\/strong> Click User Management<\/strong> and select Roles<\/strong>. This is where you set the Permissions for the Users of the various Forms and information. Click the + button to add a new Role<\/strong>.<\/p>\n\n\n\n

2)<\/strong> For each Role that you create, enter a Role Name<\/strong>, and assign the Role the appropriate Permissions<\/strong>.\u00a0The Permissions apply to each Form that you created. Lastly, click the Save button<\/strong>.<\/p>\n\n\n\n

<\/div>\n\n\n\n

All Records<\/strong> – Users of this Role can access all created Records. This includes Records that they create, and Records that other Users create. If not checked, the User will only have access to Records that they personally create.<\/p>\n\n\n\n

Create <\/strong>– The User can create New Records.<\/p>\n\n\n\n

Update<\/strong>– Users with this Permission can Update (edit) existing Records.<\/p>\n\n\n\n

View<\/strong>– The User can only View Records, they cannot edit Records.<\/p>\n\n\n\n

Delete <\/strong>– Users with Delete Permissions can delete existing Records. Once a Record is deleted it’s permanently gone (be careful with this permission setting).<\/p>\n\n\n\n

Assign<\/strong> – Users with this Permission can assign records to other members.<\/p>\n\n\n\n

<\/div>\n\n\n\n

EMPLOYEES<\/strong><\/p>\n\n\n\n

After completing your Roles, you can now add your Employees<\/strong>.<\/p>\n\n\n\n

<\/div>\n\n\n\n

It’s VERY IMPORTANT to note that when adding the Employee information, you must “use the same email address” for the employee that is used when they Register in the app.<\/strong><\/p>\n\n\n\n

1) <\/strong>Click User Management<\/strong> and select Employees<\/strong>. Next, click the blue + button<\/strong> on the right-hand-side of the screen to add a new Employee<\/strong>.<\/p>\n\n\n\n

2) <\/strong>Add the required information<\/strong> for the Employee.<\/p>\n\n\n\n

3<\/strong>) Next select a Role<\/strong> for the Employee. The Roles that you previously created will be available in the drop-down-list.<\/p>\n\n\n\n

4)<\/strong> Lastly, select if the Employee should be Active<\/strong> or if their account should be In-Active<\/strong> (preventing them from using the features). Click the Save button<\/strong> to save your settings.<\/p>\n\n\n\n

<\/div>\n\n\n\n

SETTINGS \/ TEMPLATE BUILDER<\/strong><\/h3>\n\n\n\n

In Settings<\/strong> is where you’ll find our powerful Template Builder<\/strong>. This is where you select how to display the information<\/strong> from each Form in your app. Using the Template Builder, you select which Field or Fields are displayed on the Buttons upon the App User selecting the Form.<\/p>\n\n\n\n

The methods in which you extract and display data can be simple, such as simply displaying a single record source (Form), or you can use complex methods and pull various sets of data from multiple record sources (Forms).<\/p>\n\n\n\n

<\/div>\n\n\n\n

EXTRACTING AND DISPLAYING DATA FROM A SINGLE RECORD SOURCE (FORM)<\/strong><\/h3>\n\n\n\n

Each set of records that are being pulled must begin<\/strong> with <ion-item> and end with<\/strong> <\/ion-item>.<\/p>\n\n\n\n

For example, let’s say that our Form contains the field \u201cVehicle Name\u201d<\/strong> and we want to display that data in the Report. Below is the code that we would use.  <\/p>\n\n\n\n

The label <\/strong>in the code is the Field Name <\/strong>(from the Form), and the value <\/strong>in the code is the data as entered by the App User<\/strong>.<\/p>\n\n\n\n

<ion-item> \n{{fields.Vehicle_Name.label}} {{fields.Vehicle_Name.value}}\n<\/ion-item>\n<\/code><\/pre>\n\n\n\n
The result would show like this:<\/p>\n\n\n\n
Vehicle Name Lexus<\/code><\/pre>\n\n\n\n
Realistically, may want to add a colon between the Label and Value<\/strong> so that will will display as:<\/p>\n\n\n\n
Vehicle Name: Lexus<\/code><\/pre>\n\n\n\n
To do this, you would use the code below:<\/p>\n\n\n\n
<ion-item> \n{{fields.Vehicle_Name.label}}: {{fields.Vehicle_Name.value}}\n<\/ion-item> \n<\/code><\/pre>\n\n\n\n
You can also choose not to use the<\/strong> Label <\/strong>and only use the Value such as this:<\/p>\n\n\n\n
<ion-item> \n{{fields.Vehicle_Name.value}}\n<\/ion-item>\n<\/code><\/pre>\n\n\n\n
The result would show:<\/p>\n\n\n\n
Lexus<\/code><\/pre>\n\n\n\n
<\/div>\n\n\n\n
DISPLAYING MORE THAN ONE FIELD OF DATA IN THE REPORT LIST<\/strong><\/h3>\n\n\n\n
You can display multiple Fields of data from a record source such as this:<\/p>\n\n\n\n
{{fields.Vehicle_Name.value}}\n{{fields.Model.value}}<\/code><\/pre>\n\n\n\n
The result would show:<\/p>\n\n\n\n
Lexus XF59<\/code><\/pre>\n\n\n\n
If you want to separate the fields and have them on two different lines, use the break code like this:<\/p>\n\n\n\n
{{fields.Vehicle_Name.value}}\n<br \/>\n{{fields.Model.value}}<\/code><\/pre>\n\n\n\n
The result will be:<\/p>\n\n\n\n
Lexus \nXF59<\/code><\/pre>\n\n\n\n
<\/div>\n\n\n\n
DISPLAYING MULTIPLE FIELDS OF DATA USING A DROP-DOWN LIST AS A FILTER<\/strong><\/h3>\n\n\n\n
If you have a Drop-Down field in your Form, you can use it to filter displayed data. Below is an example:<\/p>\n\n\n\n
<ion-item ng-if=\"fields.Close_Request.value=='No'\"> \n{{fields.Customer_Name.value}} \n<\/ion-item><\/code><\/pre>\n\n\n\n
In the above example, the Drop-Down field in the Form is Close Request<\/strong>… With Yes<\/strong> and No<\/strong> as the options. The code above will only display records where the App User selected No<\/strong>.<\/p>\n\n\n\n
In addition, the list will display the Customer Name<\/strong> of all records that fit the criteria.<\/p>\n\n\n\n
<\/div>\n\n\n\n
EXTRACTING AND DISPLAYING IMAGES<\/strong><\/h3>\n\n\n\n
An example of displaying an image with the field name would be:<\/p>\n\n\n\n
<ion-item> \n<img width=\"100\" src={{fields.Image_Field_Name.value}}> \n<\/ion-item><\/code><\/pre>\n\n\n\n
The 100<\/strong> in the code is the width of the image<\/strong>.<\/p>\n\n\n\n
<\/div>\n\n\n\n
SHOWING RECORDS FROM ANOTHER FORM THAT HAVE A “RELATION”<\/strong><\/h3>\n\n\n\n
If you created a Relation<\/strong> between two Forms, you can then use the Relation to extract field data from the 2nd Form. For help on creating Relations, see our documentation for our Awesome Forms feature<\/a>.<\/p>\n\n\n\n
<ion-item> \n{{relations(fields,'Related_Field_Name','Field_To_Display_Name')}} \n<\/ion-item>\n<\/code><\/pre>\n\n\n\n
Below is a real-world example of the code:<\/p>\n\n\n\n
<ion-item> \n{{relations(fields,'Customer_Name','Rented_Vehicles')}} \n<\/ion-item><\/code><\/pre>\n\n\n\n
In the code above, we have a Relation that links our Customers<\/strong> and Rented Vehicles<\/strong> using Customer Name<\/strong> as the common Field.<\/p>\n\n\n\n
You can also add an additional Field from the current Form to the Template such as:<\/p>\n\n\n\n
<ion-item> \n{{fields.name.value}} \n{{relations(fields,'Related_Field_Name','Field_To_Display_Name')}} \n<\/ion-item><\/code><\/pre>\n\n\n\n
If you want to display multiple Fields from a Related Form you can do this:<\/p>\n\n\n\n
<ion-item> \n{{fields.name.value}} \n{{relations(fields,'Related_Field_Name','Field_To_Display_Name')}} {{relations(fields,'Related_Field_Name','Field_To_Display_Name2')}} {{relations(fields,'Related_Field_Name','Field_To_Display_Name3')}} \n<\/ion-item><\/code><\/pre>\n\n\n\n
<\/div>\n\n\n\n
SHOWING RECORDS FROM ANOTHER FORM USING CONDITIONS AND RELATIONS<\/strong><\/h3>\n\n\n\n
You may need to display records from 2 different Forms using Conditions. You can use code such as:<\/p>\n\n\n\n
<ion-item ng-if=\"relations(fields,'Dropdown_Field_Name','Related_Form_Field_Name')=='Active'\" > \n{{fields.name.value}} \n<\/ion-item><\/code><\/pre>\n\n\n\n
I want to create a Report that shows me all of my Rented Vehicles that was not returned.  An example of this code would be:<\/p>\n\n\n\n
<ion-item ng-if=\"fields.Returned.value=='No'\"> \n{{relations(fields,'Customer_Name','Customer_Name') }} \n<\/ion-item><\/code><\/pre>\n\n\n\n
The top part of the code contains the Field Name and Condition that we want to use. The Field Name is Returned<\/strong>, and we only want to see records where it was set to No<\/strong>.<\/p>\n\n\n\n
The second line of code displays the Relation that we’re using (“Customer Name”), and the Customer Name<\/strong> Field that we want to display in the results.<\/p>\n\n\n\n
<\/div>\n\n\n\n
SHOWING RECORDS AND AN IMAGE FROM ANOTHER FORM USING CONDITIONS AND RELATIONS<\/strong><\/h3>\n\n\n\n
If you want to show data from another Form using a Relation, a Condition, and display an image, you can use the sample code below:<\/p>\n\n\n\n
<ion-item ng-if=\"fields.Dropdown_Field_Name.value=='No'\"> \n<img width=\"100\" src={{relations(fields,'Retlated_Field_Name','Image_Field_Name')}}> \n<\/ion-item><\/code><\/pre>\n\n\n\n
In our example, we want to show the Name and Photo of all Customers that didn’t return their Vehicle to us.<\/p>\n\n\n\n
The top part of the code contains the Conditional Field Returned<\/strong>, with the Condition as No<\/strong>.<\/p>\n\n\n\n
The bottom part of the code contains the Relation Field Customer_Name<\/strong>, and the Image Field License_Photo<\/strong>.<\/p>\n\n\n\n
<ion-item ng-if=\"fields.Returned.value=='No'\"> \n<img width=\"100\" src={{relations(fields,'Customer_Name','License_Photo')}}> \n<\/ion-item><\/code><\/pre>\n\n\n\n
<\/div>\n\n\n\n
CREATE A LINK FROM ONE FORM TO ANOTHER THAT AUTO-ADDS RELATION DATA<\/strong><\/h3>\n\n\n\n
You can add a hyperlink from one Form to another Form, that starts a new record and auto-adds Relation information.<\/p>\n\n\n\n
For example, the code below will take the App User from the Customer Information form to a new Rent record, and automatically add the Customer Name that the App User selected.<\/p>\n\n\n\n
<ion-item> \n<div ng-click=\"openConnectedForm(fields,'Form_Name')\"> Open Sample Form <\/div> \n<\/ion-item><\/code><\/pre>\n\n\n\n
In the code above, the name of the Form that should be opened is Form_Name<\/strong>. This is followed by the display text of the link: Open Sample Form<\/strong>.<\/p>\n\n\n\n
<\/div>\n\n\n\n
COLOR CODING A LINK FROM ONE FORM TO ANOTHER THAT AUTO-ADDS RELATION DATA<\/strong><\/h3>\n\n\n\n
You an add a background and text color to the link that takes you from one from to another while auto-adding Relation information. See the adjusted code below (from the example above):<\/p>\n\n\n\n
<ion-item> \n<div style=\"background-color:#be0000;color:#ffffff\" ng-click=\"openConnectedForm(fields,'Form_To_Open_Name')\"> Open Rent Form <\/div> \n<\/ion-item><\/code><\/pre>\n\n\n\n
Above, we added the following code to the link: style=”background-color:#be0000;color:#ffffff”<\/strong>. This affects the colors.\u00a0Simply change the hex code to the color code that you want to use.<\/p>\n\n\n\n
<\/div>\n\n\n\n
ADD A COLOR MESSAGE WITH A CONDITION TO A TEMPLATE<\/strong><\/h3>\n\n\n\n
You can have a message displayed on the Template based on a Condition from the Form. For example, you may want a red Customer Blocked to display in red<\/strong> if the Block Customer<\/strong> field is Yes<\/strong> in the Form.<\/p>\n\n\n\n
<ion-item> \n<div ng-style=\"fields.Block_Customer.value=='Yes' && {'background-color':'#BE0000'}\"> Active <\/div> \n<\/ion-item><\/code><\/pre>\n\n\n\n
<\/div>\n\n\n\n
ADD A COLOR MESSAGE WITH A MULTI-IF CONDITION TO A TEMPLATE<\/strong><\/h3>\n\n\n\n
You can have a message displayed on the Template based on a Condition from the Form. For example, you may want a red Customer Blocked to display in red<\/strong> if the Block Customer<\/strong> field is Yes<\/strong> in the Form. Likewise, you may want it to display green<\/strong> if the Customer Blocked<\/strong> field is No<\/strong> in the Form. Below is the example code:<\/p>\n\n\n\n
<ion-item> \n<div ng-if=\"fields.Block_Customer.value=='Yes' \"style=\"background-color:#BE0000;color:#ffffff\">Customer Blocked<\/div> \n<div ng-if=\"fields.Block_Customer.value=='No' \"style=\"background-color:#03CE2B;color:#000000\">Customer Active<\/div> \n<\/ion-item><\/code><\/pre>\n\n\n\n
<\/div>\n\n\n\n
ADD A MESSAGE WITH A MULTI-IF CONDITION TO A TEMPALTE WITHOUT COLOR<\/strong><\/h3>\n\n\n\n
You may not want to display color with your multi-if condition, if so, see the below code:<\/p>\n\n\n\n
<ion-item> \n<div ng-if=\"fields.Block_Customer.value=='Yes'\">Customer Blocked<\/div> \n<div ng-if=\"fields.Block_Customer.value=='No'\">Customer Active<\/div> \n<\/ion-item><\/code><\/pre>\n\n\n\n
<\/div>\n\n\n\n
USING AUTOMATIC FIELDS FROM THE ACCOUNT FIELD TYPE<\/strong><\/h3>\n\n\n\n
The Awesome Forms feature contains an Account<\/strong> field type that automatically adds the First Name<\/strong>, Last Name<\/strong>, and Email<\/strong> address, and ID<\/strong> of the App User using the Form, to the Form. These fields are titled:<\/p>\n\n\n\n
customer_id<\/strong><\/p>\n\n\n\n
customer_email<\/strong><\/p>\n\n\n\n
customer_name<\/strong><\/p>\n\n\n\n
When using the automatic fields, do not apply the “value” at the end of the code. For example use: {{fields.customer_email}}<\/strong> instead of {{fields.customer_email.value}}<\/strong>.<\/p>\n\n\n\n
<\/div>\n\n\n\n
DISPLAYING THE ASSIGNED FIELD IN THE TEMPLATE<\/strong><\/h3>\n\n\n\n
When using the Assign feature, one member (with the Permissions) can assign records to another member. An example of when this can be useful is with support tickets. The supervisor may want to assign a support ticket to one of the staff members.<\/p>\n\n\n\n
When using the Assign feature, a new field is automatically added to the Form that shows the email address of all Members. This is new Field is invisible to members that don’t have the Permission.<\/p>\n\n\n\n
Use the code below to display the Assigned Member’s Email Address in a Template.<\/p>\n\n\n\n
<ion-item> \n{{fields.__assigned_to}} \n<\/ion-item><\/code><\/pre>\n","protected":false},"excerpt":{"rendered":"
The CRM Data Manager is a powerful information management system that enables you to manage and coordinate various sets of data with an easy to use, front-end user interface. Our CRM works in conjunction with our Awesome Forms feature. Via Awesome Forms, the data submitted via your Forms is easily managed. You’re able to view the information in the app, and link the various sets of submitted data. In addition, the CRM enables you to easily select the methods in which you want the data linked, and you can filter the information as you see fit. USE CASE: A training school<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","knowledgebase_cat":[33],"class_list":["post-13185","knowledgebase","type-knowledgebase","status-publish","hentry","knowledgebase_cat-app-features"],"_links":{"self":[{"href":"https:\/\/buzapps.net\/info\/wp-json\/wp\/v2\/knowledgebase\/13185","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/buzapps.net\/info\/wp-json\/wp\/v2\/knowledgebase"}],"about":[{"href":"https:\/\/buzapps.net\/info\/wp-json\/wp\/v2\/types\/knowledgebase"}],"author":[{"embeddable":true,"href":"https:\/\/buzapps.net\/info\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/buzapps.net\/info\/wp-json\/wp\/v2\/comments?post=13185"}],"version-history":[{"count":13,"href":"https:\/\/buzapps.net\/info\/wp-json\/wp\/v2\/knowledgebase\/13185\/revisions"}],"predecessor-version":[{"id":15533,"href":"https:\/\/buzapps.net\/info\/wp-json\/wp\/v2\/knowledgebase\/13185\/revisions\/15533"}],"wp:attachment":[{"href":"https:\/\/buzapps.net\/info\/wp-json\/wp\/v2\/media?parent=13185"}],"wp:term":[{"taxonomy":"knowledgebase_cat","embeddable":true,"href":"https:\/\/buzapps.net\/info\/wp-json\/wp\/v2\/knowledgebase_cat?post=13185"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}