[{"data":1,"prerenderedAt":1092},["ShallowReactive",2],{"guide:en:work-fulfillment/jobs":3},{"id":4,"title":5,"body":6,"description":1084,"extension":1085,"meta":1086,"navigation":1087,"path":1088,"seo":1089,"stem":1090,"__hash__":1091},"guide_en/en/user/work-fulfillment/jobs.md","Jobs — Planning Work with Resource Requirements and Map Locations",{"type":7,"value":8,"toc":1055},"minimark",[9,14,18,53,58,68,89,93,100,172,175,179,189,194,227,233,264,269,275,284,288,291,299,302,313,316,319,324,346,351,354,359,366,371,378,381,385,388,393,407,412,430,436,450,454,459,462,468,472,475,481,485,488,494,498,501,521,527,531,538,545,549,555,558,562,568,572,578,583,588,592,601,605,636,641,658,662,667,678,683,699,704,717,721,728,753,758,766,770,773,778,789,794,805,810,821,825,830,889,895,906,909,912,916,926,944,947,951,954,1009,1012,1016,1026,1030,1035],[10,11,13],"h1",{"id":12},"jobs","Jobs",[15,16,17],"p",{},"Jobs represent individual units of planned field work, each with a map location, resource requirements (the materials and equipment the work consumes), and progress tracking. A job might be installing a junction box at a specific building, running 500 m of cable along a route, or conducting an inspection in a defined area. Jobs are versioned, so teams can plan offline, batch-create work, and roll back changes before committing to the shared dataset.",[19,20,21],"callout",{},[15,22,23,27,28,32,33,36,37,41,42,41,45,48,49,52],{},[24,25,26],"strong",{},"Jobs were called Tasks."," The §193 work-model restructure renamed the record from ",[29,30,31],"em",{},"Task"," to ",[29,34,35],{},"Job"," across the whole platform — the page, the admin rights (",[38,39,40],"code",{},"jobsCreate"," / ",[38,43,44],{},"jobsUpdate",[38,46,47],{},"jobsDelete","), and the URLs (",[38,50,51],{},"/fulfillment/jobs","). The concept is unchanged; only the name moved. Older screenshots and translations may still read \"Task\" until they are refreshed.",[54,55,57],"h2",{"id":56},"where-jobs-fit-in-the-hierarchy","Where Jobs Fit in the Hierarchy",[59,60,65],"pre",{"className":61,"code":63,"language":64},[62],"language-text","Project  (campaign grouping)\n  └── Job  ← you are here\n        ├── Resources  (materials this work consumes — optional)\n        └── Work Order  (assignment of this job to a worker or team)\n              ├── Activity line  (the work performed — registered or ad-hoc, optional)\n              └── Report  (worker's record of what was actually done)\n","text",[38,66,63],{"__ignoreMap":67},"",[15,69,70,71,74,75,78,79,82,83,88],{},"A job is the core planning record. It carries the geometry (",[24,72,73],{},"where",") and the resource requirements (",[24,76,77],{},"what materials","). Work orders assign it to people and declare the ",[24,80,81],{},"work"," to perform via their ",[84,85,87],"a",{"href":86},"/guide/work-fulfillment/activities/","activity line",". Reports fill in what was actually done, rolling progress back up to the job.",[54,90,92],{"id":91},"jobs-resources-and-activities","Jobs, Resources, and Activities",[15,94,95,96,99],{},"The §193 model splits a job's substance into two complementary registries — and both are ",[24,97,98],{},"optional",":",[101,102,103,121],"table",{},[104,105,106],"thead",{},[107,108,109,112,115,118],"tr",{},[110,111],"th",{},[110,113,114],{},"Lives on",[110,116,117],{},"Answers",[110,119,120],{},"Catalogue",[122,123,124,149],"tbody",{},[107,125,126,132,139,144],{},[127,128,129],"td",{},[24,130,131],{},"Resources",[127,133,134,135,138],{},"the ",[24,136,137],{},"job"," (resource lines)",[127,140,141],{},[29,142,143],{},"What materials/equipment does this consume?",[127,145,146],{},[84,147,131],{"href":148},"/guide/inventory-management/resources/",[107,150,151,156,162,167],{},[127,152,153],{},[24,154,155],{},"Activity",[127,157,134,158,161],{},[24,159,160],{},"work order"," (activity line)",[127,163,164],{},[29,165,166],{},"What work is being performed?",[127,168,169],{},[84,170,171],{"href":86},"Activities",[15,173,174],{},"A job does not have to declare any resources, and a work order does not have to name an activity. Declare them when structured tracking, inventory authorization, or activity-based payment earns its keep; leave them empty for simple or one-off work. Nothing forces either.",[54,176,178],{"id":177},"job-structure","Job Structure",[15,180,181,186],{},[182,183],"img",{"alt":184,"src":185},"Jobs List","/guide/work-fulfillment/tasks-list.png",[29,187,188],{},"Jobs page showing planned work with progress tracking and multi-resource requirements",[15,190,191],{},[24,192,193],{},"Basic Fields:",[195,196,197,204,210,216,222],"ul",{},[198,199,200,203],"li",{},[24,201,202],{},"Name"," — Descriptive job name",[198,205,206,209],{},[24,207,208],{},"Description"," — Detailed work instructions",[198,211,212,215],{},[24,213,214],{},"Geometry"," — Point, line, or polygon showing the work location",[198,217,218,221],{},[24,219,220],{},"Group"," — Free-text grouping within a project (e.g. \"Phase 1\", \"Electrical\")",[198,223,224,226],{},[24,225,131],{}," — Array of required materials and equipment (multi-resource support, optional)",[15,228,229,232],{},[24,230,231],{},"Resource Requirements:","\nEach resource entry includes:",[195,234,235,241,247,253],{},[198,236,237,240],{},[38,238,239],{},"resource"," — Resource definition reference",[198,242,243,246],{},[38,244,245],{},"volume"," — Quantity required",[198,248,249,252],{},[38,250,251],{},"uom"," — Unit of measure",[198,254,255,258,259,263],{},[38,256,257],{},"assignedTo"," — Person responsible for picking up this specific resource line (optional — see ",[84,260,262],{"href":261},"#per-resource-assignment","Per-Resource Assignment",")",[15,265,266],{},[24,267,268],{},"Example:",[59,270,273],{"className":271,"code":272,"language":64},[62],"Job: \"Install network junction box at Building 42\"\nGeometry: Point (lat: 40.7128, lng: -74.0060)\nResources: [\n  { resource: \"Junction Box\",    volume: 1,  uom: \"units\" },\n  { resource: \"Cat6 Cable\",      volume: 15, uom: \"meters\" },\n  { resource: \"Mounting Screws\", volume: 8,  uom: \"units\" }\n]\n",[38,274,272],{"__ignoreMap":67},[15,276,277,278,280,281,283],{},"The ",[29,279,81],{}," of installing — splicing, mounting, terminating — is recorded on the work order as its ",[84,282,87],{"href":86},", not as a resource here.",[54,285,287],{"id":286},"multi-resource-jobs","Multi-Resource Jobs",[15,289,290],{},"Prior system: one resource per job",[195,292,293,296],{},[198,294,295],{},"Problem: complex work creates excessive map markers",[198,297,298],{},"Example: 100 installations × 4 resources = 400 map points",[15,300,301],{},"Current system: multiple resources per job",[195,303,304,307,310],{},[198,305,306],{},"Single map marker represents the complete work package",[198,308,309],{},"Same example: 100 map points (one per installation)",[198,311,312],{},"Cleaner map, easier spatial planning",[54,314,262],{"id":315},"per-resource-assignment",[15,317,318],{},"Each resource line on a job can be assigned to a specific person. This lets planners designate who is responsible for picking up each material — at the line level, not just at the work-order level.",[15,320,321],{},[24,322,323],{},"How assignment works:",[195,325,326,333,336,343],{},[198,327,328,329,332],{},"In the job detail, each resource row has an ",[24,330,331],{},"Assigned To"," column",[198,334,335],{},"The column appears automatically when any row in the job carries an assignment; it stays hidden when no assignments are set",[198,337,338,339,342],{},"Assigning someone to a resource line does not reserve inventory — it records who is ",[29,340,341],{},"expected"," to pick up and deliver that item",[198,344,345],{},"Actual pickup state (who picked up, how much, when) is tracked through the transaction ledger, not on the job itself",[15,347,348],{},[24,349,350],{},"Why track at the resource level?",[15,352,353],{},"A single job can have many resource lines, and those lines may be spread across multiple work orders and crews. Per-resource assignment fills the gap: a planner can say \"Alice fetches the 50 m of conduit for this job, Bob handles the junction boxes.\" Each person gets a scoped view of exactly what they need to collect — no ambiguity about who is responsible for which item.",[15,355,356],{},[24,357,358],{},"Filtering by your resource assignments:",[15,360,361,362,365],{},"The Work Orders page has a ",[24,363,364],{},"My Resource Assignments"," filter that shows work orders whose linked job has a resource line assigned to you. Workers can use this to go straight to their specific material pickups without scanning the whole job list.",[15,367,368],{},[24,369,370],{},"Send Assignments notification:",[15,372,373,374,377],{},"Once resource assignments are set, the ",[24,375,376],{},"Send Assignments"," action on the jobs page dispatches notifications to all assignees. Each person receives a single combined message covering their work orders (name, due date, link) plus one QR code per assigned resource line. The QR code is the pickup authorization — the worker scans it at the warehouse to collect their specific item. Pickup is recorded as a transaction automatically on scan.",[15,379,380],{},"The Send Assignments action is available both as a per-row action on individual jobs and as a bulk operation when multiple jobs are selected in the table.",[54,382,384],{"id":383},"jobs-are-versioned","Jobs Are Versioned",[15,386,387],{},"Unlike work orders and reports, jobs use the version/commit workflow:",[15,389,390],{},[24,391,392],{},"Why Versioned:",[195,394,395,398,401,404],{},[198,396,397],{},"Admins design work areas offline (subway tunnels, remote sites)",[198,399,400],{},"Spatial conflict detection needed (overlapping geography)",[198,402,403],{},"Batch operations common (redesign entire campaign)",[198,405,406],{},"Rollback valuable (undo entire planning change)",[15,408,409],{},[24,410,411],{},"Workflow:",[413,414,415,418,421,424,427],"ol",{},[198,416,417],{},"Create a version (draft mode)",[198,419,420],{},"Add/edit jobs in the draft",[198,422,423],{},"Spatial validation (check for overlaps)",[198,425,426],{},"Commit version → jobs become \"official\"",[198,428,429],{},"Workers see committed jobs in assignments",[15,431,432,435],{},[24,433,434],{},"Offline Collaboration:","\nMultiple admins can create separate versions:",[195,437,438,441,444,447],{},[198,439,440],{},"Admin A: Plan north region jobs",[198,442,443],{},"Admin B: Plan south region jobs",[198,445,446],{},"Both work offline, commit later",[198,448,449],{},"Conflict resolution if geographies overlap",[54,451,453],{"id":452},"job-geometry-types","Job Geometry Types",[455,456,458],"h3",{"id":457},"point-jobs","Point Jobs",[15,460,461],{},"Single location work (equipment installation, inspection).",[59,463,466],{"className":464,"code":465,"language":64},[62],"Geometry: { type: \"Point\", coordinates: [lng, lat] }\n",[38,467,465],{"__ignoreMap":67},[455,469,471],{"id":470},"line-jobs","Line Jobs",[15,473,474],{},"Linear work (cable runs, pipeline installation).",[59,476,479],{"className":477,"code":478,"language":64},[62],"Geometry: { type: \"LineString\", coordinates: [[lng1,lat1], [lng2,lat2], ...] }\n",[38,480,478],{"__ignoreMap":67},[455,482,484],{"id":483},"polygon-jobs","Polygon Jobs",[15,486,487],{},"Area-based work (coverage zones, service areas).",[59,489,492],{"className":490,"code":491,"language":64},[62],"Geometry: { type: \"Polygon\", coordinates: [[[lng1,lat1], ...]] }\n",[38,493,491],{"__ignoreMap":67},[54,495,497],{"id":496},"proximity-filtering","Proximity Filtering",[15,499,500],{},"Find jobs near specific locations:",[413,502,503,506,512,515,518],{},[198,504,505],{},"Open the Jobs page",[198,507,508,509],{},"Click ",[24,510,511],{},"Filter Nearby",[198,513,514],{},"Drag the map marker to a location",[198,516,517],{},"Set distance (e.g., 5 km)",[198,519,520],{},"Table shows only jobs within that radius",[15,522,523,526],{},[24,524,525],{},"Row Action:"," click \"Filter Nearby\" on a job row → auto-sets proximity to that job's location.",[54,528,530],{"id":529},"job-usage-in-work-orders","Job Usage in Work Orders",[15,532,533,534,537],{},"Each work order links to ",[24,535,536],{},"one job"," — the specific job the worker is being assigned to execute. Work orders cannot span multiple jobs; if work crosses job boundaries, create a work order per job or use ad-hoc standalone work orders.",[15,539,540,541,544],{},"A job can be referenced by ",[24,542,543],{},"multiple work orders"," — useful when splitting a large job across several crews or when work is phased over multiple days.",[15,546,547],{},[24,548,268],{},[59,550,553],{"className":551,"code":552,"language":64},[62],"Job: \"Run cable on floor 3\"\n  Resources: 200m cable\n\nWork Order A (Morning crew):\n  Job: \"Run cable on floor 3\"\n  Resource Targets: 100m cable\n  Activity: Pull fibre — 100m\n\nWork Order B (Afternoon crew):\n  Job: \"Run cable on floor 3\"\n  Resource Targets: 100m cable\n  Activity: Pull fibre — 100m\n",[38,554,552],{"__ignoreMap":67},[15,556,557],{},"Both work orders reference the same job; reports from both roll into the job's progress calculation.",[54,559,561],{"id":560},"job-progress-tracking","Job Progress Tracking",[15,563,564,567],{},[24,565,566],{},"Calculation:","\nProgress = Average completion across all resource lines",[15,569,570],{},[24,571,268],{},[59,573,576],{"className":574,"code":575,"language":64},[62],"Job with 2 resources:\n  - Cat6 Cable: 10m required, 5m completed = 50%\n  - Screws: 8 required, 8 completed = 100%\n\nOverall progress = (50% + 100%) / 2 = 75%\n",[38,577,575],{"__ignoreMap":67},[15,579,580],{},[24,581,582],{},"Visual Indicators:",[195,584,585],{},[198,586,587],{},"Progress bar: Green ≥ 100%, Yellow ≥ 50%, Red \u003C 50%",[54,589,591],{"id":590},"creating-jobs","Creating Jobs",[15,593,594,597,598,600],{},[24,595,596],{},"Access Required:"," ",[38,599,40],{}," admin right",[15,602,603],{},[24,604,411],{},[413,606,607,610,613,618,621,624,627,630,633],{},[198,608,609],{},"Navigate to Fulfillment → Jobs",[198,611,612],{},"Create a new version (or edit an existing draft)",[198,614,508,615],{},[24,616,617],{},"Add Job",[198,619,620],{},"Fill basic info (name, description)",[198,622,623],{},"Click the map to set geometry",[198,625,626],{},"Add resource lines if the work consumes materials (optional, can add multiple)",[198,628,629],{},"Set per-resource assignments if needed",[198,631,632],{},"Save the job in draft",[198,634,635],{},"Commit the version when planning is complete",[15,637,638],{},[24,639,640],{},"Best Practices:",[195,642,643,646,649,652],{},[198,644,645],{},"Group related materials in a single job (reduces map clutter)",[198,647,648],{},"Use consistent naming (e.g., \"Install — Junction Box — Building 42\")",[198,650,651],{},"Set realistic resource volumes (informs inventory planning)",[198,653,654,655,657],{},"Capture the ",[29,656,81],{}," on the work order's activity line, not as a pseudo-resource",[54,659,661],{"id":660},"bulk-job-generation","Bulk Job Generation",[15,663,664],{},[24,665,666],{},"Method 1: Import from GeoJSON",[413,668,669,672,675],{},[198,670,671],{},"Create a GeoJSON file with one feature per job",[198,673,674],{},"Each feature carries properties: name, description, resources",[198,676,677],{},"Import → creates all jobs in one version",[15,679,680],{},[24,681,682],{},"Method 2: Generate from Map Selection",[413,684,685,688,693,696],{},[198,686,687],{},"Select existing features on the map",[198,689,508,690],{},[24,691,692],{},"Generate Jobs",[198,694,695],{},"Choose a resource configuration",[198,697,698],{},"One job created at each selected location",[15,700,701],{},[24,702,703],{},"Method 3: Duplicate a Job",[413,705,706,709,714],{},[198,707,708],{},"Select a job with the correct resource configuration",[198,710,508,711],{},[24,712,713],{},"Duplicate",[198,715,716],{},"Edit the geometry to the new location",[54,718,720],{"id":719},"batch-print-jobs","Batch Print Jobs",[15,722,723,724,727],{},"A project may contain dozens or hundreds of jobs. Rather than printing each one from its detail page, use the project-level ",[24,725,726],{},"Print all jobs"," action:",[413,729,730,736,741,747,750],{},[198,731,732,733,263],{},"Open the parent project's detail page (",[38,734,735],{},"/fulfillment/projects/:id",[198,737,508,738,740],{},[24,739,726],{}," in the header",[198,742,743,744],{},"The batch print view opens at ",[38,745,746],{},"/fulfillment/jobs/batch/[ids]",[198,748,749],{},"Screen shows 10 jobs per page (paginated, CSS-driven — all records are in the DOM so printing emits everything)",[198,751,752],{},"Print the page — each job is separated by a hard page break",[15,754,755],{},[24,756,757],{},"Notes:",[195,759,760,763],{},[198,761,762],{},"Safety cap: the batch view is limited to 200 jobs per print run. If the project exceeds this, a banner warns you and jobs beyond 200 are truncated — split the print into smaller batches if needed.",[198,764,765],{},"Each job renders with the same layout as its individual job page.",[54,767,769],{"id":768},"job-validation","Job Validation",[15,771,772],{},"Before a version is committed, the system validates:",[15,774,775],{},[24,776,777],{},"Spatial Conflicts:",[195,779,780,783,786],{},[198,781,782],{},"Overlapping polygons (two jobs covering the same area)",[198,784,785],{},"Point jobs too close together (configurable threshold)",[198,787,788],{},"Line jobs crossing restricted zones",[15,790,791],{},[24,792,793],{},"Resource Availability:",[195,795,796,799,802],{},[198,797,798],{},"Warning if required resources are not in inventory",[198,800,801],{},"Doesn't block commit (jobs may be future-dated)",[198,803,804],{},"Helps procurement planning",[15,806,807],{},[24,808,809],{},"Geometry Validity:",[195,811,812,815,818],{},[198,813,814],{},"Points must have valid coordinates",[198,816,817],{},"Lines must have at least 2 points",[198,819,820],{},"Polygons must close (first point = last point)",[54,822,824],{"id":823},"job-work-order-lifecycle","Job → Work Order Lifecycle",[15,826,827],{},[24,828,829],{},"Typical Flow:",[413,831,832,838,844,850,856,862,868,874],{},[198,833,834,837],{},[24,835,836],{},"Planning"," — Admin creates jobs in a draft version",[198,839,840,843],{},[24,841,842],{},"Commit"," — Version committed, jobs become official",[198,845,846,849],{},[24,847,848],{},"Work Order"," — A work order is created, linking to this job, declaring its activity, and assigning it to a worker",[198,851,852,855],{},[24,853,854],{},"Execution"," — Worker executes the job, possibly over multiple work orders",[198,857,858,861],{},[24,859,860],{},"Reporting"," — Worker submits a report referencing this job",[198,863,864,867],{},[24,865,866],{},"Progress"," — Job progress updates based on all reports referencing it",[198,869,870,873],{},[24,871,872],{},"Completion"," — When all resources reach 100%, the job is effectively complete",[198,875,876,879,880,883,884,888],{},[24,877,878],{},"Graduation"," — If the completing work order has a ",[24,881,882],{},"Graduates To"," layer set, the job's geometry is placed or moved on the map (see ",[84,885,887],{"href":886},"#job-graduation","Job Graduation"," below)",[15,890,891,894],{},[24,892,893],{},"Job Reuse:","\nJobs can be referenced by multiple work orders:",[195,896,897,900,903],{},[198,898,899],{},"Split large jobs across multiple crews",[198,901,902],{},"Partial completion by one worker, finished by another",[198,904,905],{},"Progress aggregated across all reports",[54,907,887],{"id":908},"job-graduation",[15,910,911],{},"Job graduation is how completed field work becomes part of the shared GIS dataset. When a work order that links to a job is completed, it can automatically place or advance the job's geometry on the map.",[455,913,915],{"id":914},"setting-up-graduation","Setting Up Graduation",[15,917,918,919,921,922,925],{},"In the work order create or edit form, set the ",[24,920,882],{}," field to the target layer. When that work order is marked ",[38,923,924],{},"completed",", the graduation hook fires:",[195,927,928,938],{},[198,929,930,933,934,937],{},[24,931,932],{},"No existing map feature"," → a new feature is created in the target layer, using the job's geometry and properties. A ",[38,935,936],{},"sourceJobId"," link is stamped on the feature for traceability.",[198,939,940,943],{},[24,941,942],{},"Existing map feature"," → the feature is moved to the target layer. The feature retains the same ID — nothing is duplicated.",[15,945,946],{},"The job itself is never deleted or archived. It remains as the permanent planning and work record.",[455,948,950],{"id":949},"multi-stage-graduation","Multi-Stage Graduation",[15,952,953],{},"A job can graduate through multiple layers as successive work orders complete. Example for a fibre network installation:",[101,955,956,968],{},[104,957,958],{},[107,959,960,962,965],{},[110,961,848],{},[110,963,964],{},"Target Layer",[110,966,967],{},"Stage",[122,969,970,983,996],{},[107,971,972,975,980],{},[127,973,974],{},"Survey",[127,976,977],{},[38,978,979],{},"planned-routes",[127,981,982],{},"Route confirmed on map",[107,984,985,988,993],{},[127,986,987],{},"Installation",[127,989,990],{},[38,991,992],{},"installed-routes",[127,994,995],{},"Cable physically in place",[107,997,998,1001,1006],{},[127,999,1000],{},"Acceptance",[127,1002,1003],{},[38,1004,1005],{},"accepted-routes",[127,1007,1008],{},"Sign-off complete",[15,1010,1011],{},"Each completion just re-points which layer shows the job's geometry — no re-linking of the job itself is needed.",[455,1013,1015],{"id":1014},"graduation-log","Graduation Log",[15,1017,1018,1019,1022,1023,1025],{},"The job detail view → ",[24,1020,1021],{},"Location"," tab shows a ",[24,1024,1015],{},": a timestamped timeline of every layer move, including which work order triggered each transition. Use this to audit the lifecycle of a field installation.",[54,1027,1029],{"id":1028},"viewing-job-details","Viewing Job Details",[15,1031,1032],{},[24,1033,1034],{},"Job Detail Page Shows:",[195,1036,1037,1040,1043,1046,1049,1052],{},[198,1038,1039],{},"Basic information and geometry",[198,1041,1042],{},"Resource requirements list with per-resource assignment",[198,1044,1045],{},"Progress bar and percentage",[198,1047,1048],{},"Work orders referencing this job (with their activity lines)",[198,1050,1051],{},"Reports that have recorded work against this job",[198,1053,1054],{},"Graduation log (Location tab)",{"title":67,"searchDepth":1056,"depth":1056,"links":1057},2,[1058,1059,1060,1061,1062,1063,1064,1070,1071,1072,1073,1074,1075,1076,1077,1078,1083],{"id":56,"depth":1056,"text":57},{"id":91,"depth":1056,"text":92},{"id":177,"depth":1056,"text":178},{"id":286,"depth":1056,"text":287},{"id":315,"depth":1056,"text":262},{"id":383,"depth":1056,"text":384},{"id":452,"depth":1056,"text":453,"children":1065},[1066,1068,1069],{"id":457,"depth":1067,"text":458},3,{"id":470,"depth":1067,"text":471},{"id":483,"depth":1067,"text":484},{"id":496,"depth":1056,"text":497},{"id":529,"depth":1056,"text":530},{"id":560,"depth":1056,"text":561},{"id":590,"depth":1056,"text":591},{"id":660,"depth":1056,"text":661},{"id":719,"depth":1056,"text":720},{"id":768,"depth":1056,"text":769},{"id":823,"depth":1056,"text":824},{"id":908,"depth":1056,"text":887,"children":1079},[1080,1081,1082],{"id":914,"depth":1067,"text":915},{"id":949,"depth":1067,"text":950},{"id":1014,"depth":1067,"text":1015},{"id":1028,"depth":1056,"text":1029},"Jobs represent individual units of planned field work — installing equipment, running cable, inspecting infrastructure — placed on the map with defined resource requirements and tracked through completion. Jobs were renamed from Tasks in the §193 work-model restructure.","md",{},true,"/en/user/work-fulfillment/jobs",{"title":5,"description":1084},"en/user/work-fulfillment/jobs","i7R5rB7WS4eCc0IjlEr0d3eyRMHaRseKWz9_D8LaTrw",1781607716214]