| 1. |
This is the suite of workflow commonly used for policies This workflow module suite depends on the following Nav Items, Roles, Data Sources, and Forms. The template gallery was configured to load them in the following order (given that Many records depend upon roles, which is why roles is first in the list. All Records, as they are released to the site will bear the prefix 'Workflow -', and all items will live under one navigation item entitled:
|
| 2. |
|
| 3. |
|
| 4. |
|
| 5. |
|
| 6. |
|
| 7. |
|
| 8. |
|
| 9. |
|
| 10. |
|
| 11. |
|
| 12. |
|
| 13. |
|
| 14. |
|
| 15. |
|
| 16. |
|
| 17. |
|
| 18. |
This file contains complete code examples for Actionable EXT Module Designer implementations. Use these for data-centric views requiring grid tables, bulk actions, export functionality, and administrative controls.
|
| 19. |
|
| 20. |
**Architecture rule:** A Centralpoint Module Designer always binds to its own
|
| 21. |
|
| 22. |
|
| 23. |
|
| 24. |
|
| 25. |
|
| 26. |
|
| 27. |
|
| 28. |
|
| 29. |
|
| 30. |
|
| 31. |
|
| 32. |
|
| 33. |
|
| 34. |
|
| 35. |
|
| 36. |
|
| 37. |
|
| 38. |
|
| 39. |
|
| 40. |
|
| 41. |
|
| 42. |
|
| 43. |
|
| 44. |
|
| 45. |
|
| 46. |
|
| 47. |
|
| 48. |
|
| 49. |
|
| 50. |
|
| 51. |
|
| 52. |
|
| 53. |
|
| 54. |
|
| 55. |
|
| 56. |
|
| 57. |
|
| 58. |
|
| 59. |
|
| 60. |
|
| 61. |
|
| 62. |
|
| 63. |
|
| 64. |
|
| 65. |
|
| 66. |
|
| 67. |
|
| 68. |
|
| 69. |
|
| 70. |
|
| 71. |
|
| 72. |
|
| 73. |
|
| 74. |
|
| 75. |
|
| 76. |
|
| 77. |
|
| 78. |
|
| 79. |
|
| 80. |
|
| 81. |
|
| 82. |
|
| 83. |
|
| 84. |
|
| 85. |
|
| 86. |
|
| 87. |
|
| 88. |
|
| 89. |
Centralpoint modules can be customized through a **Module Configuration XML** file (CustomModuleConfig.xml) that defines additional fields beyond the base module schema. Custom fields that extend beyond the standard release are stored in the `cpsys_D
|
| 90. |
|
| 91. |
|
| 92. |
|
| 93. |
|
| 94. |
|
| 95. |
|
| 96. |
|
| 97. |
|
| 98. |
|
| 99. |
|
| 100. |
|
| 101. |
|
| 102. |
|
| 103. |
|
| 104. |
|
| 105. |
|
| 106. |
|
| 107. |
|
| 108. |
|
| 109. |
|
| 110. |
|
| 111. |
Purpose This policy establishes authoritative expectations, controls, and accountability for communications basics policy. It ensures that all internal and external communications are accurate, respectful, timely, and aligned with organizational objectives, risk appetite, and legal and regulatory obligations. The policy reduces the likelihood that ad-hoc or informal practices will create safety, security, privacy, compliance, reputational, or ser
|
| 112. |
|
| 113. |
|
| 114. |
|
| 115. |
|
| 116. |
|
| 117. |
|
| 118. |
|
| 119. |
|
| 120. |
|
| 121. |
|
| 122. |
|
| 123. |
|
| 124. |
|
| 125. |
|
| 126. |
|
| 127. |
|
| 128. |
|
| 129. |
|
| 130. |
|
| 131. |
|
| 132. |
|
| 133. |
|
| 134. |
|
| 135. |
|
| 136. |
|
| 137. |
|
| 138. |
|
| 139. |
|
| 140. |
|
| 141. |
|
| 142. |
|
| 143. |
|
| 144. |
|
| 145. |
|
| 146. |
|
| 147. |
|
| 148. |
|
| 149. |
|
| 150. |
|
| 151. |
|
| 152. |
|
| 153. |
|
| 154. |
|
| 155. |
|
| 156. |
|
| 157. |
|
| 158. |
|
| 159. |
|
| 160. |
|
| 161. |
|
| 162. |
|
| 163. |
|
| 164. |
|
| 165. |
|
| 166. |
|
| 167. |
|
| 168. |
|
| 169. |
|
| 170. |
|
| 171. |
|
| 172. |
|
| 173. |
|
| 174. |
|
| 175. |
|
| 176. |
|
| 177. |
|
| 178. |
|
| 179. |
|
| 180. |
|
| 181. |
|
| 182. |
|
| 183. |
|
| 184. |
|
| 185. |
|
| 186. |
|
| 187. |
|
| 188. |
|
| 189. |
|
| 190. |
|
| 191. |
|
| 192. |
|
| 193. |
|
| 194. |
|
| 195. |
|
| 196. |
|
| 197. |
|
| 198. |
|
| 199. |
|
| 200. |
|
| 201. |
|
| 202. |
|
| 203. |
|
| 204. |
|
| 205. |
|
| 206. |
|
| 207. |
|
| 208. |
|
| 209. |
|
| 210. |
|
| 211. |
|
| 212. |
These are hard-won lessons from production front-end development inside Centralpoint DataSources. Each one causes invisible failures, broken styling, or unexpected behavior. Read before writing any Template Content, Item Content, or inline JavaScript
|
| 213. |
|
| 214. |
Module Designers are the stylesheets/templates that control how records from any Centralpoint module are displayed to end users. Located under **Site Architecture** in the Centralpoint Client Console, Module Designers allow completely different prese
|
| 215. |
This skill provides help documentation for Centralpoint modules features.
|
| 216. |
|
| 217. |
|
| 218. |
|
| 219. |
|
| 220. |
|
| 221. |
|
| 222. |
|
| 223. |
|
| 224. |
|
| 225. |
|
| 226. |
|
| 227. |
|
| 228. |
|
| 229. |
|
| 230. |
|
| 231. |
|
| 232. |
|
| 233. |
|
| 234. |
|
| 235. |
|
| 236. |
|
| 237. |
|
| 238. |
|
| 239. |
|
| 240. |
|
| 241. |
|
| 242. |
The Oxcyon Centralpoint SDK provides .NET class libraries for extending and integrating with the Centralpoint CMS platform.
|
| 243. |
This skill documents the **complete 6-file pattern** for building a Centralpoint ACTION EXT Module Designer: a data-centric grid with checkbox selection wired to a 3-step Wizard Action Form that performs bulk operations (Change Attributes, Move Modul
|
| 244. |
|
| 245. |
|
| 246. |
|
| 247. |
|
| 248. |
|
| 249. |
|
| 250. |
|