Wallboard League Tables Application
- or -
Post a project like this$$
- Posted:
- Proposals: 3
- Remote
- #1728968
- Expired
Description
Experience Level: Intermediate
General information for the business: League Tables for Company Statistics
Kind of development: New program from scratch
Description of every module: We use an application for logging or sales and support tickets called Autotask which has a web api that can pull data from the Autotask database. I will do this part of the application.
What I need is some to help me with the framework and the layout to display on our TV's. I am using Wordpress with this plugin: https://codecanyon.net/item/league-table/7578593 for the table design.
I need a number of tables in the system that will cycle through on a timer and options where we can change the gap between moving to the next league (one setting/number for all)
Description of requirements/functionality: I need each page to have an area where I can insert the Autotask code which will be similar to the following:
$query = new ATWS\AutotaskObjects\Query('Ticket');
$package = new ATWS\AutotaskObjects\QueryField('CreateDate');
$package->addExpression('greaterthan', "02/09/2017");
$package4 = new ATWS\AutotaskObjects\QueryField('CreateDate');
$package4->addExpression('lessthan', "06/09/2017");
$package2 = new ATWS\AutotaskObjects\QueryField('Title');
$package2->addExpression('NotLike', "%Automated Backup Notification:%");
$package3 = new ATWS\AutotaskObjects\QueryField('Title');
$package3->addExpression('NotLike', "%Success%");
$package5 = new ATWS\AutotaskObjects\QueryField('Title');
$package5->addExpression('NotLike', "%Your email to Daisy Wholesale%");
$query->addField($package);
$query->addField($package2);
$query->addField($package3);
$query->addField($package4);
$query->addField($package5);
$result = $client->query($query);
$entities = $result->queryResult->EntityResults->Entity;
$count = 0;
foreach ($entities as $entity) {
print($entity->Title . "");
//code to enter into our database here
$count = $count + 1;
}
print "";
print $count;
As I have said I will be writing the above, but I will need a space left to do this. All I need doing is the framework, the database design and the code to enter the results into the database.
The part where you see foreach ($entities as $entity) this is where it will output to the league table and enter the records into a mysql database.
This is how I imagine it will be done, but it is open to discussion:
We need to have one main page of code. The url will contain which loop we are on. The loop number is held in the database.
Each league table will have an ID which is the loop number we are on. We also want a dropdown at the top which will allow us to manually select a particular page which will of course assign the loop number in the url.
Each time a league table is loaded it will record the information into a MySQL database. The page will look back at the last 4 days and the current data to make sure all stats are correct. This is because we will load the leagues on Monday but the pages will not be loaded on Saturday or Sunday.
At the end of each page I will need the code to write to the Autotask data to MySQL. You can do this by just doing var1, var2, var3 etc. I will make the fields be in those variables.
We need to be able to go back in history using a query that we can pop open from the side, I.e. this shouldn’t always be available.
All Autotask code should be in includes file, if blah = 1 etc
League Tables
ID 1 - Staff table – StaffID, First name, Last name, email address, position, start date
This is a static table that will only record the current members of staff, i.e. it will not record history. i.e. it will empty and update each time. This is just a simple list.
ID 2 - Active Support Clients table – CompanyID, Company name, address, postcode
This is a static table that will only record the current members of staff, i.e. it will not record history. i.e. it will empty and update each time. This is just a simple list.
ID 3 - Sales table – SalesID, Company ID, StaffID, , Reason, Amount, Reoccurring Y/N
This is a simple list. If it goes onto 2 pages then it must use the next page as say ID 3a and show it next.
ID 4 - Sales per person per month – Month, StaffID, Amount
This table will show a list of months January – December across the top and down the side will be list of employees from ID 1. Each box will show the amount.
etc (ran out of room so will email the other IDs to the successful bidder)
We need to be able to add these websites in admin.
CMS and Admin requirements: We need this to be in a section of the blank Wordpress website which is already installed with the Leagues plugin also installed.
Ideally the code will be on one page with an ID number in the database to say which league is currently showing on refresh. We also need to be able to extend a sidebar to go back in history
Kind of development: New program from scratch
Description of every module: We use an application for logging or sales and support tickets called Autotask which has a web api that can pull data from the Autotask database. I will do this part of the application.
What I need is some to help me with the framework and the layout to display on our TV's. I am using Wordpress with this plugin: https://codecanyon.net/item/league-table/7578593 for the table design.
I need a number of tables in the system that will cycle through on a timer and options where we can change the gap between moving to the next league (one setting/number for all)
Description of requirements/functionality: I need each page to have an area where I can insert the Autotask code which will be similar to the following:
$query = new ATWS\AutotaskObjects\Query('Ticket');
$package = new ATWS\AutotaskObjects\QueryField('CreateDate');
$package->addExpression('greaterthan', "02/09/2017");
$package4 = new ATWS\AutotaskObjects\QueryField('CreateDate');
$package4->addExpression('lessthan', "06/09/2017");
$package2 = new ATWS\AutotaskObjects\QueryField('Title');
$package2->addExpression('NotLike', "%Automated Backup Notification:%");
$package3 = new ATWS\AutotaskObjects\QueryField('Title');
$package3->addExpression('NotLike', "%Success%");
$package5 = new ATWS\AutotaskObjects\QueryField('Title');
$package5->addExpression('NotLike', "%Your email to Daisy Wholesale%");
$query->addField($package);
$query->addField($package2);
$query->addField($package3);
$query->addField($package4);
$query->addField($package5);
$result = $client->query($query);
$entities = $result->queryResult->EntityResults->Entity;
$count = 0;
foreach ($entities as $entity) {
print($entity->Title . "");
//code to enter into our database here
$count = $count + 1;
}
print "";
print $count;
As I have said I will be writing the above, but I will need a space left to do this. All I need doing is the framework, the database design and the code to enter the results into the database.
The part where you see foreach ($entities as $entity) this is where it will output to the league table and enter the records into a mysql database.
This is how I imagine it will be done, but it is open to discussion:
We need to have one main page of code. The url will contain which loop we are on. The loop number is held in the database.
Each league table will have an ID which is the loop number we are on. We also want a dropdown at the top which will allow us to manually select a particular page which will of course assign the loop number in the url.
Each time a league table is loaded it will record the information into a MySQL database. The page will look back at the last 4 days and the current data to make sure all stats are correct. This is because we will load the leagues on Monday but the pages will not be loaded on Saturday or Sunday.
At the end of each page I will need the code to write to the Autotask data to MySQL. You can do this by just doing var1, var2, var3 etc. I will make the fields be in those variables.
We need to be able to go back in history using a query that we can pop open from the side, I.e. this shouldn’t always be available.
All Autotask code should be in includes file, if blah = 1 etc
League Tables
ID 1 - Staff table – StaffID, First name, Last name, email address, position, start date
This is a static table that will only record the current members of staff, i.e. it will not record history. i.e. it will empty and update each time. This is just a simple list.
ID 2 - Active Support Clients table – CompanyID, Company name, address, postcode
This is a static table that will only record the current members of staff, i.e. it will not record history. i.e. it will empty and update each time. This is just a simple list.
ID 3 - Sales table – SalesID, Company ID, StaffID, , Reason, Amount, Reoccurring Y/N
This is a simple list. If it goes onto 2 pages then it must use the next page as say ID 3a and show it next.
ID 4 - Sales per person per month – Month, StaffID, Amount
This table will show a list of months January – December across the top and down the side will be list of employees from ID 1. Each box will show the amount.
etc (ran out of room so will email the other IDs to the successful bidder)
We need to be able to add these websites in admin.
CMS and Admin requirements: We need this to be in a section of the blank Wordpress website which is already installed with the Leagues plugin also installed.
Ideally the code will be on one page with an ID number in the database to say which league is currently showing on refresh. We also need to be able to extend a sidebar to go back in history
David K.
99% (22)Projects Completed
32
Freelancers worked with
29
Projects awarded
31%
Last project
16 Nov 2020
United Kingdom
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
Can you make few rough visuals for me to see. This is a bit hard to visualize but i got the idea of what you want
511019
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies