RolePay Time Clock Expansion - Revision history

Johnny: Added "clocked_in_count" API action

2021-02-24T20:43:06Z

Added "clocked_in_count" API action

2020-11-17T18:46:54Z

2019-04-08T23:55:07Z

2019-04-08T16:11:04Z

2019-02-21T01:08:11Z

2019-02-20T04:01:35Z

2018-06-09T19:24:20Z

2018-04-11T21:22:36Z

2018-04-11T02:02:09Z

2017-02-15T23:40:37Z

@@ Line 152: / Line 152: @@
 === Information required for API call ===
-* action (payout_everyone)
+* action (payout_user)
 * api_key
 * user_uuid (The user you're wanting to pay out)
@@ Line 163: / Line 163: @@
+{
      "success":"johnny nexen was successfully paid $27."
+}
 </pre>

@@ Line 168: / Line 168: @@
 = '''<span style="color:#4D5A93">Changelog</span>''' =
 <b><span style="color:red">** UPGRADE INSTRUCTIONS **</span></b>
-<p>If you already have a Time Clock set up and would like to continue using that network, you'll have to copy the network key located in the description field of your old time clock. (The Network Key begins with an '@' character, followed by 36 characters)<br/><b>Once you have copied the network key</b>, you can paste the key into the description field of the new time clock. Once set, left-click the time clock and it should automatically connect to your network.</p>
+<p>If you already have a Timeclock set up and would like to continue using that network, you'll have to copy the network key located in the description field of your old timeclock. (The Network Key begins with an '@' character, followed by 36 characters)<br/><b>Once you have copied the network key</b>, you can paste the key into the description field of the new timeclock. Once set, left-click the timeclock and it should automatically connect to your network.</p>
@@ Line 181: / Line 186: @@
 * <b><u>Version 1.1</u></b>:
 * <b>New Feature:</b> Admin login; you can now assign admins and allow them access to the dashboard.
 * <b>New Feature:</b> Time Conditions; set specific working hours a person can work for each day of the week.
 * <b>Fixed:</b> Auto-Clockout; users with 'auto-clockout' enabled should now be properly clocked out when they go offline.

@@ Line 126: / Line 126: @@
+{
      "success": "User has successfully been clocked out."
+}
 </pre>

@@ Line 62: / Line 62: @@
 === HTTP API Call ===
-<pre>http://rolepay.timeclock.morethanpixels.rocks/api/action/check_key/api_key/{API_KEY} GET</pre>
+<pre>http://rolepay.timeclock.mtp.onl/api/action/check_key/api_key/{API_KEY} GET</pre>
 === Example Response ===
@@ Line 82: / Line 82: @@
 === HTTP API Call ===
-<pre>http://rolepay.timeclock.morethanpixels.rocks/api/action/register_user/api_key/{API_KEY}/user_uuid/{USER_UUID}/wage/{USER_WAGE} GET</pre>
+<pre>http://rolepay.timeclock.mtp.onl/api/action/register_user/api_key/{API_KEY}/user_uuid/{USER_UUID}/wage/{USER_WAGE} GET</pre>
 === Example Response ===
@@ Line 101: / Line 101: @@
 === HTTP API Call ===
-<pre>http://rolepay.timeclock.morethanpixels.rocks/api/action/clock-in_user/api_key/{API_KEY}/user_uuid/{USER_UUID} GET</pre>
+<pre>http://rolepay.timeclock.mtp.onl/api/action/clock-in_user/api_key/{API_KEY}/user_uuid/{USER_UUID} GET</pre>
 === Example Response ===
@@ Line 120: / Line 120: @@
 === HTTP API Call ===
-<pre>http://rolepay.timeclock.morethanpixels.rocks/api/action/clock-out_user/api_key/{API_KEY}/user_uuid/{USER_UUID} GET</pre>
+<pre>http://rolepay.timeclock.mtp.onl/api/action/clock-out_user/api_key/{API_KEY}/user_uuid/{USER_UUID} GET</pre>
 === Example Response ===

@@ Line 132: / Line 132: @@
 = '''<span style="color:#4D5A93">Changelog</span>''' =
 * <b><u>Version: 1.3</u></b>:
 * <b>New:</b> Moved to new server

@@ Line 131: / Line 131: @@
 = '''<span style="color:#4D5A93">Changelog</span>''' =
-* <b><u>Version: 1.2</u></b>:
+* <b><u>Version: 1.3</u></b>:
 <b><span style="color:red">** PLEASE READ BEFORE YOU UPDATE **</span></b>
 <p>If you already have a Time Clock set up and would like to continue using that network, you'll have to copy the network key located in the description field of your old time clock. (The Network Key begins with an '@' character, followed by 36 characters)<br/><b>Once you have copied the network key</b>, you can paste the key into the description field of the new time clock. Once set, left-click the time clock and it should automatically connect to your network.</p>
 * <b>Fixed:</b> Fixed security issue with URLs

@@ Line 13: / Line 13: @@
 <p>These steps assume that you already have an API key.<br />Follow these steps to configure your device:</p>
 #Locate the Time Clock in your inventory and rez into place
 #Left-click the Time Clock to receive the dialog menu &amp; select "Setup"
 #A URL dialog will be presented, offering you a link to the online device registration page
@@ Line 28: / Line 27: @@
 *<b>Work Days:</b> Allows you to check the boxes of the week days the user is permitted to work. <b>Note:</b> The system conducts <b>midnight</b> checks; if the user is not permitted to work the new day, they'll be clocked out automatically
 <br />
 = '''<span style="color:#4D5A93">Clocking Out Users</span>''' =

← Older revision		Revision as of 02:02, 11 April 2018
Line 125:		Line 125:
	}		}
	</pre>		</pre>
		+
		+
		+	= '''<span style="color:#4D5A93">Changelog</span>''' =
		+	* <b>Version 1.1</b>:
		+
		+	<b><span style="color:red"> PLEASE READ BEFORE YOU UPDATE </span></b>
		+	<p>If you already have a Time Clock set up and would like to continue using that network, you'll have to copy the network key located in the description field of your old time clock. (The Network Key begins with an '@' character, followed by 36 characters)<br/><b>Once you have copied the network key</b>, you can paste the key into the description field of the new time clock. Once set, left-click the time clock and it should automatically connect to your network.</p>
		+
		+
		+	* <b>New Feature:</b> Admin login; you can now assign admins and allow them access to the dashboard.
		+	* <b>New Feature:</b> Time Conditions; set specific working hours a person can work for each day of the week.
		+	* <b>Fixed:</b> Auto-Clockout; users with 'auto-clockout' enabled should now be properly clocked out when they go offline.